LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

db tools create parameterized query

I have a working Oracle data insertion/updating vi that works beautifully within Windows 2000, Oracle Client 8.1.7 Release 3....using System DSN's that are proven. Trying to use it on Windows XP to the same database via Oracle Client 8.1.7 Release 3, I get an error:
Exception occured in ADODB.Connection, Provider does not support the property..in Conn Get Properties.vi->Db Tools Create Parameterized Query.vi
 
I am posting the actual subroutine that I use, although please understand that there is a seperate connection and command subroutines that feed this one. This one is where the error occurs.. again, only on XP. Works fine in 2000. All using LV 7.1 and Database Conenctivity 1.0.1
 
 
0 Kudos
Message 1 of 7
(4,165 Views)
Hello,
 
It sounds like perhaps you have different versions of the database ADO (ActiveX Data Object) underneath, and the version you have on your XP machine doesn't support a propery we're using underneath.  Can you check the version of the ADO you're using on each machine, and compare?  Also, can you troubleshoot down into the Db Tools Create Parameterized Query.vi to see which property is generating the error?
 
Thanks, and I hope we can track down this problem soon!
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
0 Kudos
Message 2 of 7
(4,132 Views)
Hello again,
 
Ok, I have an idea for how me might get around this.  Can you try using a UDL instead of a DSN?  For the Provider, I think you'll need to use "Microsoft OLE DB Provider for Oracle."  Here are a few links to more information on this:
 
LabVIEW-Related:
 
General:
I hope this helps!
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
Message 3 of 7
(4,113 Views)
The error happens in the "Conn Get Properties.vi" at the output of the property node within. I'll try the suggestions tomorrow then will be gone till the middle of next week. I do appreciate the advice! Thanks
0 Kudos
Message 4 of 7
(4,108 Views)
Sounds great, and I hope the UDL approach works around the problem!
 
Repost with whatever your results are and we'll keep exploring this if necessary!
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
0 Kudos
Message 5 of 7
(4,090 Views)
I was able to sucessully implement the UDL connection process which solved the problem. Thanks to JLS. 🙂

Message Edited by dg99 on 09-20-2006 09:55 PM

0 Kudos
Message 6 of 7
(4,022 Views)
Excellent!
 
Thanks for the update - it'll help others in the future know that this can be a solution!
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
0 Kudos
Message 7 of 7
(4,003 Views)