Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Gary Quiring — — source: Usenet: comp.databases.informix
We use MS Access 2000, 2002 & 2003 with our IDS 7.3 engine with no issues using
Intersolv 3.11 drivers. We have an IDS 9.4 server waiting in the wings because
we cannot get ODBC / MS Access to work. We upgraded to ODBC 3.82 from IBM.
We get a variety of inconsistant errors. The only semi working solution is to
format the PC and load a fresh copy of WinXP with SP2. Any upgrades from prior
releases of ODBC don't work.
But even with reloading the PC we still get issues that we cannot recreate. On
some days you cannot double click a linked table in Access. All the rows are
returned with # signs with ODBC failed error. (No error code). Reboot the PC
and it might work. Wait a day and the results will change. (I know Billyware!!)
Now here is where it gets intesting. Take the same query in Access and run it
in Excel and it ALWAYS works!! Excel has zero issues.
Are there better drivers that we can use?
Thanks
Gary Quiring
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.