Converting Access 2 VBA code into access 2000 1

[joebickley]

Hi

Im have me lumbered with a rather extensive Access 2 database fresh from the stone age. I need to convert it to access 2000. There is reams and reams of VBA code in it and when i convert the database over to 2000 much of it does not work, as i expected.

Are there any references i can make to allow the old code to work under 2000?

Most of the code that does not work is where they have use the TABLE datatype to look for records in tables. I know the code to use instead of it but i really dont want to have to go through it all swaping it around.

Any help would be great
Joe Bickley

 

[LittleSmudge]

As a quick and dirty fix you can link in the DAO libraries

2.5/3.5 Compatibility Library might be a good place to start.


Did you make sure that the A2 database was fully compiled in A2 before you converted it ?




G LS
accessaceNOJUNK@valleyalley.co.uk
Remove the NOJUNK to use.

Please remember to give helpful posts the stars they deserve!
This makes the post more visible to others in need! :-D

 

[joebickley]

Your a star i knew i could do it i had actually tried something similar but i chose the wrong one

I bow down to your knowledge!!!!

Thansk you

 

[DavidHoareau]

As says GLS, you must convert all table and query access in your VBA. Ex : Stop to use the Snashot data type and replace it with Recordest Type. You'll must change the object methode too : CreateSnapshot() doesn't exist any more... I'm actually work on a same problem to convert a a very full VBA code iron age access 97 to access 2000. All it over, but the database run very very slowly ! Why ? If you have an idea, please, give me answer : david_hoareau@yahoo.fr.

Thank a lot

David Hoareau

 

[KenReay]

Hi

Not sure if this in connected to your problem, but I have seen several reports of speed problems in A2K, with split FE/BE applications on networks. This is alledgedly caused by the treatment of the (.ldb).

The recomended work around is to have a hidden form which is openned on application load, and which opens a table (and thus keeps it open) for the duration of the application.

This supposedly cuases the .ldb file to be openned and kept open for the duration of the application.

I have no personal experience of the problem, or the suggested solution, so I cannot say either way

Hope this helps

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
UK