Question Converting to Access 2007

[Tallbloke]

Will converting an Access 2003 to 2007 database break anything?

I know that's a bit general but are there any major pitfalls to be aware of?

 

[pbaldy]

I've converted a number of 2000 db's with no major issues. Sometimes goofy little things like reports that displayed perfectly suddenly need a textbox or two widened because they're displaying #####. Same printer, so I assume 2007 renders slightly differently than 2000 did. I don't think you'll have any big issues.

 

[Trevor G]

Do you have VBA in the database, is it linked to other applications or coded to them? Converting upwards should always work but also need to check if VBA is used and how.

 

[kbear954]

I've only ever had a problem if having to go backward when working on a different machine (because why else would you back-step?) But Trevor G makes a good point - make sure you know all of the links and VBA to ensure everything is still active.

I would back up somewhere seperate from the newly updated machine. That way if anything does go wonky - you have an unsullied copy of the DB to fall back on.

 

[Tallbloke]

Thinking some more about it, I'm not sure there is much need, everything works just fine and the changes I am making aren't huge.

That said, I am working on a separate copy of the front and back ends of the database. I know I can just copy over the front end on user machines and everything will be fine. What I was wondering is if there is a way to copy a new table structure without over writing or losing date. I'm sure there is, but it's not something I want to mess up without double and triple checking

And it goes without saying I will be backing up everything before I make any live changes