I have a VB5 app that produces an Access Violation exception error on an NT4
server (with SP3) during a read of an Access 2.0 table ONLY when the table
HAS data.  If the table is empty, you don't get any errors.  This happens
after the app has just finished a read/write to another Access 2.0 table
which confuses the {*filter*}out of me.  It works fine on Win95/98 and on another
NT4 test server.  I've tried having user login as Administrator.

I am opening the recordset using an SQL statement.  I do have VB5 SP3.  I am
using the DAO 2.5/3.5 Compatibility layer reference.  Any ideas???

On another NT4 server, if the table has data I get a different Exception
'Memory Read' error ...'Memory block cannot be read.

What's the deal??