Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Using DAO Recordset Object in MS Excel to Query Citadel

Everytime I try to use the Connection.OpenRecordset method in VB for Excel, it causes a Dr. Watson error on my system and Excel crashes. Has anyone experienced similar behavior on their systems? When I run the same query using the MSQuery object the data is returned without any problems.

Regards,
Derek
0 Kudos
Message 1 of 3
(3,671 Views)
Derek,

Citadel 4's ODBC driver is not fully SQL 92 complient and has probably some restrictions.
E.g. you can not write to the database through ODBC and therefore you might open the database as read only... To figure out where could be the problem you might contact National Instrument's support team.

Before doing that you might consult the two examples you might be able to use with VBA as well and a good explanation about the limitation of Citadel 4.


Good example using Data object: Querying Citadel 4 Via ODBC in Microsoft Visual Basic

A good answer on the discussion forum about ervlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000B40E0000&UCATEGORY_0=_51_%24_6_...


Good example using ADO interface:
Querying Citadel 4 Via OLE DB Provider for ODBC in Microsoft Visual Basic


Hope this helps.
Roland.

PS: Citadel 5's ODBC driver that comes with LabVIEW DSC Module (I think it's not (yet?) available for Lookout) conforms SQL 92 standards.
Message 2 of 3
(3,671 Views)
Roli,

Thanks for the help. By perusing the OLE DB example I found the error of my ways :-). Thanks for your suggestions.

Regards,
Derek McClure
0 Kudos
Message 3 of 3
(3,671 Views)