cursor behavior

First of all we woulf liker to thank those who helped us getting ODBC to work. The solution ended up being for us to use the OpenLink drivers (took all of 10 minutes to get working versus a week+ for the Informix-CLI drivers!). We now have a question regarding behavior of cursors when linking to tables via ODBC call from an Access 97 application. Whenever we do a remote view of table with any cursor movement through it (including modifications and deletes) we are getting a "Fetch attempt on unopen cursor: -400" error. Does Access have the ability to define a cursor whenever a remote table is called via ODBC-- without having to write a module. We could certainly do this via ESQL in C, but am wondering if this would even be necessary. For what it's worth the OpenLink drivers do support JetEngine level calls. Thanks in advance! -- Greg Silverman <gms@tc.umn.edu> University of Minnesota Cancer Center