Converting from 2000 to 2003 - help!

[converse]

We have a couple of quite complex systems (I maintain the code) designed in A2000 SP3, our IT dept is finally moving us to the Office 2003 platform, so we want to convert the Access systems over. (Separate front end and back end, all secured with a workgroup file)

Some of the code uses DAO which I'll re-write in ADO to make fully up to date.

When I open these systems for testing in Access 2003 I receive the Macro warning dialogue, what is the best way of suppressing this / signing the systems to say they are safe? As we don't want the users having to deal with it!

Are there any other major issues to be concerned about, the front ends will be compiled as MDEs once fully "ok" in A2003. Backends will remain MDBs.

 

[boblarson]

Some of the code uses DAO which I'll re-write in ADO to make fully up to date.

No need to do that. 2003 uses DAO just fine. Just make sure that there is a reference set to it and that you explicitly refer to things like

Dim db As DAO.Database
Dim rst As DAO.Recordset

instead of

Dim rst As Recordset

When I open these systems for testing in Access 2003 I receive the Macro warning dialogue, what is the best way of suppressing this / signing the systems to say they are safe? As we don't want the users having to deal with it!

You might want to go to this page:
http://office.microsoft.com/en-us/access/HA011225981033.aspx

Are there any other major issues to be concerned about, the front ends will be compiled as MDEs once fully "ok" in A2003. Backends will remain MDBs.

If you install Office 2003 Service Pack 3, make sure to install the Post SP3 hotfix:
http://support.microsoft.com/kb/945674
Also it would be good to remove any formatting at table level and only format in your queries, forms, and reports.

 

[converse]

Many many thanks will have a read!