AccessDiscussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.

Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .

Hope the sages among you can help me.
We have quite complex Access databases that have grown over the years. They are generally split - front end and backend.
The code has been developed from Access 97, through to MS Access XP but based on Access 2000 file db format. Shortly to be upgraded to MS Access 2003 and sitting on a MS Server 2003. Coding is mainly Jet DAO with the odd ADO.
MS Access security is not implemented although there are multi-users attached.
The system is now creaking and we will be shortly upgrading to SQL, possibly to the recent announced MS SQL Express.
Sorry for the lengthy introduction but the nux of my query is:
"What is the best way for me to convert the existing systems?"
Any tips, references and experience would be very welcome.

Thanks for the quick reply Brian.
By DAO I mean most of my references to datasets in the Dim statement are left open i.e. the dataset is not declared and therefore are defaulted as Variant and DAO datasets.
I know this is lazy but has served me well for years.
I get the impression that these would need converting to ADO and connections set up to SQL. This could be quite a lot of effort.
Still welcome further feedback from any of you.