Up till now I have opened the environment, first, and then used the environment to bring in the project or vi. Is there something written somewhere by National Instruments that guarantees a 32-bit development will never enter a 64-bit environment unless it is specifically requested to do such? I see a danger of a 32-bit development being accidentally converted to 64-bit via an errant save. Is the danger unfounded? Am I just being a worry wart? Am I free to open a 32-bit vi without fear? Now you may ask, why should there ever be an errant save? (I hear 'just be careful about the save button you noob peasant!') It has been my experience that splats (*) follow projects that haven't been modified simply because "an attribute has changed" -- this being the only explanation given when one can't just exit without being prompted to save or not. But I didn't change anything! Too bad. Choose. ...technically, there is still Task Manager to abort all NI products to avoid answering the undesired question... So, am I just paranoid of the side-by-side 64-bit installation? My apologies if this topic has already been covered, here. I couldn't find the answer to the question.

LabVIEW

Not sure if it solves (or tries to solve) the TestStand situation.

Given its price you might give it a try.

Message 31 of 31

(122 Views)

What do you need our team of experts to assist you with?

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?