Hi! - I have a database written in Access97 with some Vba coding. It is split into FE/BE and I want to put it onto 2 other pc's (standalone) where it will eventually be used. One Pc runs Access 2000 and the other Access 2003. When this is done I don't need the 97 version. Are there any issues I should look out for on initial conversion? Any further development will be done in the 2000 version - what are the subsequent issues installing updates to the 2003 version.

Thanks for any help/advice
Ian

Ian the biggest theproblem area you will have to deal with is the macros, they seem to change from version to version and I have heard several people calling them colorful metifores. Next maybe the report, specially if you have graphs and linke OLE stuff in them. Make a copy before you start, you may need it. Check out everything after the update. LOL, hth.

Hi! - thanks for the info. This database only has 1 macro - thanks to this site!!! There are some reports but not graphs of Ole stuff yet. What about ADO/DAO Objects - I've read somewhere that these change?

Thanks again
Ian

The ADO/DAO you mentioned refers to any code you have that uses the DAO object. Here are a couple of ways around them:

1) change any code you have that uses DAO to ADO, however this can be tricky if you are unfamiliar with ADO, and can require a lot of changes to existing code

2) Tick the reference in Tools-References (while looking at a code window) Microsoft DAO 3.6 Object Library.

It is a good idea, no matter which method you use to explicity declare which object you are using, eg

Instead of using something like

Dim dbs as Database

do this instead

Dim dbs as DAO.Database

or if you decide to use ADO then

Dim rst As ADODB.Recordset
Dim cnn As ADODB.Connection

Most of the books I have read will say that ADO is a far better method to use, but it could be a large job to convert existing code to use the ADO object. Reason being, you can't just put ADO. in front of all your variables, because the methods in ADO are different to those used in DAO eg, you couldn't do this:

Dim dbs As ADODB.Database

because ADO doesn't have a .Database method

HTH

Hi Mitch - Thanks for the quick reply. I haven't an enormous amoungt of code at present - I was waiting to get the database onto 2000 or 2003 before adding the "luxuries"!!! Your Option 2 seems the better bet until I learn some more about ADO.

Thanks again
Ian

Just one thing, if you don't add the explicit references to DAO in you're code using method 2, you will need to make sure that the Microsoft DAO 3.6 object Library is HIGHER up in the list of references than Microsoft ActiveX Data Objects 2.1 Object Library otherwise access will still use ADO as the default if you don't specify which one you wish to use in code.

HTH

Here is a link to some more info on Converting An Access File

Wow!!! So much info!!! I am finding this an amazing site. Any problems and the answer is immediately forthcoming-doing wonders for my database design! Thanks for the info and the link - that'll keep me quiet for a minute or two ;-)

Ian

No problem