I have a multiuser table, approx 20 users.  It was running on windows 3.1,
(access 2.0 table, DAO 2.5) has operated for 4 years no probs.   5000+
records, inc. large memos. Company is upgrading to WinNT4, one user changed
over, installed NT4, immediately corrupting table on save. (strange
characters in memo fields!)
I am porting app. to 32.bit, (access 8.0) changing all api calls to return
longs etc.
Using VB4, should I reference DAO 3.5 or stick with DAO 3.0.
I know there is a bit of a bug on the update command, and I can only use
.update dbupdateregular,false.   but, does anyone know if there are any
other issues using DAO 3.5 with VB4.

Thanks

I have a multiuser table, approx 20 users.  It was running on windows 3.1,
(access 2.0 table, DAO 2.5) has operated for 4 years no probs.   5000+
records, inc. large memos. Company is upgrading to WinNT4, one user changed
over, installed NT4, immediately corrupting table on save. (strange
characters in memo fields!)
I am porting app. to 32.bit, (access 8.0) changing all api calls to return
longs etc.
Using VB4, should I reference DAO 3.5 or stick with DAO 3.0.
I know there is a bit of a bug on the update command, and I can only use
.update dbupdateregular,false.   but, does anyone know if there are any
other issues using DAO 3.5 with VB4.

Thanks