Converting background code from Access 2000 to 2007

[PaulA]

Hi, all--

I've just been getting aclimated to Access 2007 with some years of doing minimun Access work at all. I have an old A2K application with significant coding that I want to convert to 2007.

It seems that all the code behind my forms and reports doesn't migrate to 2007.

How does one convert the code to 2007? I did some initial web research but haven't found anything useful.

Thanks!

Paul

 

[vbaInet]

Most of your code should be portable. Not a great deal has been deprecated. I don't think there's any tool that can do this for you but you might be lucky.

In general, you may find this link useful:

http://allenbrowne.com/access2007.html

 

[PaulA]

Thanks for your response.

Here's the deal--

It seems that when I open an A2K in 2007, it messes up the original database. I have to reinstall Office 2000, copy the objects into a blank database and then the new database will work.

If I open the new A2K file in 2007, the same thing will happen.

It seems that 2007 corrupts my original file, and it definately doesn't convert.

Any thoughts?

 

[vbaInet]

What you can do is, open it in 2007 but don't run any forms, queries, code or whatever. Convert it to 2007, then Save As 2000.

 

[PaulA]

The corruption occurs when I open the database in 2007. I get lots of different error messages like one saying the code cannot be read.

And thats when I go back to open the file in A2K and all the forms (and reports, I guess) are corrupted and won't function as coded.

I now have to create a new file and import the objects from the source file into a blank DB from the original source DB (A2K) which is still not corrupted.

I should also say that I get a office "hybrid" program that runs when opening 2007 after having 2000 open, and then a similar program when going back to 2000 from 2007.

 

[boblarson]

Personally I would just convert it by IMPORTING everything into a blank ACCDB shell. It solves a lot of conversion problems that way. Yes, you'll have to go set your startup options and all again but it is worth it.

 

[PaulA]

Duh...

I actually got to that same conclusion right as I got your response.

There are some kinks to work out, but it seems to be basically OK.

Thanks for your help.

 

[gemma-the-husky]

i would be concerned if it doesnt convert.

i dont think i have had any problemes converting older systems nlcuding A97 to A2007

there may be an issue with libraries, especially ADO/DAO. But they wouldnt corrupt your code

 

[chrisroyfilms]

I agree the best way to upgrade your database is to create a new blank document, import all of your forms/macros/tables etc. and then setup the start up options and such. I have taken a database from 2000 to 2003 to, just recently, 2007 and had few issues.
Of course the important thing is to test everything to make sure none of your macro's or vb code contain depreciated functions. It does happen, but you can usually figure those out.

 

[Simon_MT]

I agree with Dave, the only problem was DAO and changes in syntax, but that was easily fixed. This was a conversion from Access 97 to Access 2007, apart from the above, I was surprised how well the multitude of Functions transferred to 2007.

Simon