|
-
May 21st, 2001, 03:55 PM
#1
Thread Starter
Lively Member
Access97 on a Access2000 machine
We just delivered an app developed using VB/Access97 to a customer who has Access2000 on his Win98 machine. Included in the distributed files was DAO350.DLL.
When the customer executes a piece of code that calls for a delete (MyDB.Execute "DELETE * FROM myTable;"), the program errors with an error code of 0 (I think that's an automation error).
Anyone want to try this one???
-
May 21st, 2001, 04:44 PM
#2
Frenzied Member
As long as no one opened the DB in Access 2000 and converted it, everything should work fine. If someone converted it, then there is a different story.
-
May 21st, 2001, 06:05 PM
#3
Hmmm, similar problem.
seoptimizer is right, and yes we hit the same problem. You need to develop in Access 2000, and include DAO 3.6 in your distribution. Haven't testing this as yet, but apparently is backwardly compatiable with Access97.
Anyone want to guess we will have even more problems with Access XP, which can be fixed with a download, 13 service packs, and a hundred dollar note to the Gates foundation. I am getting mightly sick of MSs bulls**te.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|