Re: ODBC Problem

Greetings: I've seen this error running directly on the server, through informixs dbaccess tool. As I recall, the informix db engine returns more than one error code to indicate a contention problem. This error code and associated message indicate the row you are after is locked in some manner. This scenario matches the fact that you don't see the problem until you connect to a busier (more users) database. Hope this helps. In article <3smjcn$mun@cssun.mathcs.emory.edu>, Scott.Allred@nsc.sprint.com wrote: > }Subject: ODBC Problem > }Author: informix-list-owner@rmy.emory.edu at INTERNET > }Date: 6/26/95 7:21 AM > } > } > }I have an interesting problem with Informix I-Net > }and Q+E ODBC driver. > } > }All is installed correctly and works as it should > }with a SMALL database, a dozen or so tables, but as > }soon as I create a Datasource to our main database I > }get the error: > } > >Could not do index read to get next row > } > }This has me stumped somewhat. Does anyone have any ideas??? > }The database in question would have approx. >200 tables in > }it. > } > }After re-reading the above it is somewhat of a short story > }but straight to the point. I am hoping that someone has > }come across this before. > } > }Thanks in advance for any assistance on this one. > > What applications are you using the ODBC connection with? Visual Basic, MS > Access 2.0, ... > > Make sure you have a unique primary key on each table in you database. > Hope that helps. > > +--------------------------------------------------------------------+ > | Scott Allred Internet: scott.allred@nsc.sprint.com | > | Sprint/North Supply AOL: kujaahawk@aol.com | > | New Century, KS MSN: kujayhawk@msn.com | > | USA Phone: (913) 791-7000 x1810 | > | Fax: (913) 791-7671 | > +--------------------------------------------------------------------+ -- charlie_sadler@mathworks.com