Access Violation error on NT4 during DAO read of Access 2.0 table 
Author Message
 Access Violation error on NT4 during DAO read of Access 2.0 table

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??

Sat, 12 May 2001 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. VB5 app using DAO causes access violation when shut down on NT4.0

2. Reading Access 2.0 db on network w/read-only access

3. access violation during install

4. Access Violation in NT4.0

5. Access Violation in NT4.0

6. VB4: permission to read MS Access 2.0 SysObject table from VB

7. Access Violation in NT4.0

8. Access Violation in NT4.0

9. VB5/DAO 3.5 read-only access to attached tables

10. Help: Problem reading Access 2.0 mdb from VB3 under Win95/Access 7.0


12. Error updating attached MS-Access 2.0 tables


Powered by phpBB® Forum Software