Access 97 to 2000 compilation errors 1

[dkaplan]

I receive the error: "Compilation errors during conversion" when trying to convert my Access 97 database to 2000. The forms in the database use quite a lot of DAO code. I have tried all of the follwing to no avail: 1. Selecting "Microsoft 3.6 object library" on the reference list, 2. deselecting "DAO 2.5..." from the missing list, then repeating 1, 3. re-registering dao360.dll. I also tried to paste dao350.dll (the old NT version) into the DAO directory, but Windows 2K wouldn't let me.

Suggestions?

 

[ghubbell]

Yes indeed.. If you still can, open the old version just to see its references and the order they're in. Try taking your new Db and making another new Db from it. Do a compile and find out if/when/where the snags are. You may also require a reference to MS VB for Apps extensibility 5.3. Same deal, watch the priority! Gord
ghubbell@total.net

 

[dkaplan]

Thanks, Gord.

Actually, the only thing that seemed to work was moving over one of the references from the original application in Access 97. It was a file called: DAO2535.tlb. Doing this necessitated de-selecting DA0360.dll, which I gather is the 2k version of DAO2535. (Running them both causes a conflict.) Everything seems to work, except my queries are now slow beyond belief. Is this to be expected in Access 2000?

 

[ghubbell]

Thanks d, and no you're supposed to be getting better as we performance. Unless you're running 16 table queries on 10,000 records, I think you should investigate further. Are you able to compile now? How about a compact~repair? BTW don't use the compact on close switch. Too many problems. Try the idea though of a new empty Db. I had a 97 conversion that took 4 steps before it finally got all the wires back in line. Keep at it...it'll go! Gord
ghubbell@total.net

 

[dkaplan]

Yes, it does compile. Upon further investigation, the slow query response seems connected to the use of dlookup in some of the queries. It's puzzeling, as my 97 version had no problem with dlookup.

Thanks for your help.

Dennis

 

[MichaelRed]

dkaplan,

Not specifically w/ the 2K, but I have ALWAYS seen performance go to ... using any of the domain aggregate functions in Ms. Access. I have always gotten beter performance by writting a whole normal query for the domain aggregates than using the intrinsic functions.


MichaelRed
redmsp@erols.com

There is never time to do it right but there is always time to do it over