Hello!
We're committed to linking multiple LabVIEW test-apps to a [relational/SQL] DB via ODBC(DAO.) However, LabVIEW's implementation of ODBC(DAO) _seems_ fragile and I'm hesitant to trust that the DCT won't have the same [underlying] issues.
The attached VI exhibits three different behaviours under XP/LabVIEW 7.1, Win2K/LabVIEW 7.1, Win2K/LabVIEW 6.1.
XP/7.1 - Exception @ OpenRecordset
Win2K - 7.1 - Works
Win2K - 6.1 - Invalid Pointer @ Variant To Data (Note, skipping 1st rec w/MoveFirst-MoveNext, returns without error - or first rec.)
VI assumes a "PTDB" Datasource is defined and references a DB with a "Table1". Also, the Active-X "BEngine" class may need to be re-established - see Type Library\"Microsoft DAO 3.6..."
Seeking the wisdom of anyone using the DCT - what's your environment (OS/LabVIEW ver.) Have you observed any platform-specific problems?
Anyone using a Non-Active-X-reliant method of interfacing with [relational/SQL] DB?
Thanks
When they give imbeciles handicap-parking, I won't have so far to walk!