MDB to ADP conversion (95->98->2000mdb>2000adp) 1

[WahTeasEWah]

Over the past few years I've converted an extensive frontend MDB from Access95 to Access98 then to Access2K. The backend has gone over a Gig so I reacently did the upsize wizard. I am now have an adp file where the code no longer works and before I start reading and learning the proper Access2K way of interfacing to the database, and more so to get the thing working again, is there an easy way to make the current code work?, i.e.

set dbs = CurrentDb

no longer sets and so further code can't use it.

I'm sure there are others.

I'm changing the frontend to Virtual C, but that will take sometime and I just want to speed up this pig using the "simple" upsizing wizard.

...I have a feeling I'm stuck learning ADO...

If there is anyone who has gone through this, give me a couple of hints.

Thanks in advance for any help.

 

[TimKThailand]

Since DAO is not available in ADP, you have to move to ADP.

If you will move to VC finally, why don't you use MDB as a frontend and use SQL Server as a backend for the time being? Make sure you use a pass thru query to optimize the backend.