bad linkage to method

[RobBoyer]

Hello LabVIEW gurus,

I've got an issue with some invoke node calls to the Microsoft ADO (version 2.7) API in order to manage database communications.  The issue is that it seems that the linkage only works on one of my development machines at a time.  If I compile the VIs on one machine, everything is fine, but if I then move it to the other machine and force a re-compile, all of the ADO invoke node calls get greyed out and I get a broken arrow due to the "bad linkage to method" error.  Of course, I can then relink the node and then everyone is happy again, but then I get the problem on the first machine.  I could go back and forth all day, but I can't get it to be re-compilable on both machines.  ADO 2.7 is installed on both machines and I have never had this issue using other programming languages.  Any suggestions?

Note that I'm not sure how big a deal this is - so far, despite not being able to re-compile, the code actually works.  So, so far at least it has been more of an annoyance than anything else, but I'm concerned about potential versioning conflicts if it is for some reason using a different version of ADO on one of the machines.

I'm using LabVIEW 7.0.  Any suggestions will be greatly appreciated.

Rob

[tst]

---

RobBoyer wrote:

Any suggestions will be greatly appreciated.

---

Use MDAC 2.8 (or any newer version, if available)?

[RobBoyer]

Hi tst,

MDAC 2.81 (which is the latest version) is installed with Windows XP SP2, which happens to be the OS on both of the PCs.  I haven't explicitly tried using different versions of ADO (for example "upgrading" to 2.8) primarily because version 2.7 is the version that has the feature set that I'm looking for and it has been quite solid for me in the past.

Ah well, I guess I could try repairing MDAC, but it seems unlikely to me that MDAC is corrupted since I've had no other problems.

Thanks for the suggestion anyway,

Rob