Re: Windows ODBC driver for IDS 9.4 Help

Gary Quiring wrote: > 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 So you are using Access as your development environment with IDS as your backend? If Excel works, and the ODBC drivers are the same, then Access is the problem. If Access is just your programming environment I would suggest using something else, Borland Delphi is very good for database development. (www.borland.com/Delphi) I've been trying it using various components (ADO, BDE, and IDAC) and ADO is the slowest. I'm using IBM Connect for the ODBC drivers for all components. Access is really only good for smaller scale databases and only a few users. I don't like Informix much either. I will be converting to Firebird soon (it is easy, excellent, and free). www.ibphoenix.com -- _________________________________________ Don Gollahon dlgllhn@InHisStepsSoftware.com ICQ#: 115831669 "What in Eternity does it matter?" _________________________________________

On Tue, 04 Jan 2005 23:59:36 -0600, "Don Gollahon" <dlgllhn@NoSpamInHisStepsSoftware.com> wrote: > >So you are using Access as your development environment with IDS as >your backend? If Excel works, and the ODBC drivers are the same, then >Access is the problem. If Access is just your programming environment >I would suggest using something else, Borland Delphi is very good for >database development. (www.borland.com/Delphi) I've been trying it >using various components (ADO, BDE, and IDAC) and ADO is the slowest. >I'm using IBM Connect for the ODBC drivers for all components. > >Access is really only good for smaller scale databases and only a few >users. > >I don't like Informix much either. I will be converting to Firebird >soon (it is easy, excellent, and free). www.ibphoenix.com That is not practical since we already have a large amount of code written in Access. Our main development is 4GL. But like many companies we have limited resources for programming. So a few of our power users developed their own queries and reports in Access. It has grown over the years. We cannot simply switch to something else. It has worked fine for years. Considering how popular MS Office is IBM should do a better job of making their products compatible with it. Gary