Problem in a VI changing from 32 to 64 bits

[billko]

---

@Sergey_Kolbunov wrote:
LabVIEW 32-bit under Win7 64-bit OS should be right to use 32-bit dlls.

---

But - at least by my interpretation - he was using LV 2011 64 bit.

[rolfk]

I think the 32 bit and 64 bit DLL debate is a non-issue in this specific case. IMAQ Vision is available for both and if the wrong DLL was used it wouldn't crash at runtime but the IMAQ Vision VIs would be broken at load-time and never would allow the application to be run.

[billko]

I thought that it crashes and returns an error about running a 32 bit dll in a 64 bit application.

[JMadariaga]

---

billko escribió:

I thought that it crashes and returns an error about running a 32 bit dll in a 64 bit application.

---

No, it doesn't.

Just to make things clear in case it helps and anyone has any idea:

The program worked in 32bit labview running in a 32bit Windows 7 computer.

Now, when calling certain IMAQ Vision functions (such as IMAQ BCG lookup.vi) LabVIEW crashes and  gives no reason, just closes. This happens in both LabVIEW 32 and 64 bit BUT running in a 64bit Windows 7 computer.

We are sure that we do not have any broken wires or error in data type when the program runs,...

These are the only things that we know for sure.

Thank you all for the comments.

Julene

[billko]

---

@JMadariaga wrote:

---

billko escribió:

I thought that it crashes and returns an error about running a 32 bit dll in a 64 bit application.

---

No, it doesn't.

Just to make things clear in case it helps and anyone has any idea:

The program worked in 32bit labview running in a 32bit Windows 7 computer.

Now, when calling certain IMAQ Vision functions (such as IMAQ BCG lookup.vi) LabVIEW crashes and  gives no reason, just closes. This happens in both LabVIEW 32 and 64 bit BUT running in a 64bit Windows 7 computer.

We are sure that we do not have any broken wires or error in data type when the program runs,...

These are the only things that we know for sure.

Thank you all for the comments.

Julene

---

Sorry, of course you guys are right.  I haven't worked so long with this issue, I had forgotten that that message pops up in edit mode when you first try to use it.

Thank you for restating your problem.  This is definitely different than what I was envisioning.

[JesusG]

You can check this link for further information:

http://www.ni.com/white-paper/10383/en/

Jesús