So a guy goes into his doctors office and tells his doctor "Ya gotta
help me doc...it hurts when I run my head into the door like
this...OW!". Then the doctor says:
"DON'T DO THAT ANY MORE!!!" 🙂
(I promise to keep my day job...oops what job...and not go into
comedy..)
Why don't you convert all the old 16 bit code into 32 bit code and
create one application where the various parts all know about each
other? I don't think that there's any way to coordinate an old 16 bit
LV and a new 32 bit LV application so that they don't step on each
other driverwise like they appear to be doing. I don't think that the
two LabVIEW's even know that the other exists!
Alternatively, get a second computer to run the 16 bit code on and
make the two apps communicate with
each other using TCP/IP or serial.
Doug De Clue
ddeclue@bellsouth.net
cincidude wrote in message news:<506500000008000000E4550000-1027480788000@exchange.ni.com>...
> I am using 2 versions of Labview at the same time, one is version 4
> which has a camera and a weigh-in-motion scale attached to it. The
> second is either Labview version 4, 16-bit or Labview 3.0.1, 16-bit,
> i'm not sure. The sixteen bit has a data acquisition system attached
> to it. Its an optim electronics system and the 16-bit Labview drivers
> for the optim were provided by Optim electronics and so I am stuck
> with using the same system. When I use both these systems in tandem,
> the system crashes frequently, but both systems run fine
> independently. It usually just freezes up or says "Illegal operation
> performed. Contact program vendor". Its a windows error with a red
> cross.
