Link to home
Create AccountLog in
Avatar of slam69
slam69Flag for United Kingdom of Great Britain and Northern Ireland

asked on

Upgrade from 2000 to 2007

Hi all,

The business i work in have just decided to upgrade from office 2000 to 2007. Marvellous news obviouswly, but they have several bespoke access db's built in 2000 and a couple of sql dbs with access 2000 front ends. in addition to this they have a huge amount of excel sheets with embedded queries and vba behind the,

My experiences with 2007 is non-existent and company policy means I cannot get hold of a test machine until we begin the upgrade procedure, crazy i know.

im looking for peoples experiences with these upgrades so i can plan for any issues we are going to encounter

I know you dont HAVE to convert the db's from 2000 to 2007 but is it beneficial, if you dont is it as easier as with 2003 to accidnelty convert the db and then not be possible to roll it back to the earlier format?

any problems with teh access front ends to sql?

Does excel 2007 have the embedded query functionality the same as 2000 and has anyone run into issues with vba code not running on newer versions?

thanks for your help with this, like i said teh upgrade starts soon and its frightening the amount of legacy bits and bobs lying around here


SOLUTION
Avatar of Gustav Brock
Gustav Brock
Flag of Denmark image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
ASKER CERTIFIED SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
A "policy" against a test machine? Now what is that?

/gustav
Avatar of slam69

ASKER

Policy is nto against test machine, im just not allowed to install the application until IT start tp upgrade the machiens within teh network, they are testing office 2007 within their area and as logn as it doesnt impact on the image used for the OS then it is approved for deployment until then it cant be used even for testing, can you see why im looking into a job change

@Rorya-- thanks for the info... i do have a lot of chart manipulation and creation performed vby VBA, is it just library references that need manipulating or will teh whole VBA need rewriting?

Any yes they are quite mad, they are pushing to move to sql for all data storage which is fine and im moving stuff as i find it but its the volume that we are dealing with thats causing me a nightmare, might be time to let the problem hit and then they can see what monster they have created
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Avatar of slam69

ASKER

Well I got hit with it today and im going for a meeting with the senior management tomorrow when im going to push to get teh upograde across all our areas suspended until I have tested all eventualities, it wont happen but at least my butt is covered for telling them there will be problems...

Thanks for the help guys im going to split the points as you all have provided bits for me to consider

thanks guys

Jay
In theory your chart code ought to be compatible, pretty much 100%. In practice, it will almost certainly run slower and there will probably be a few quirks as the new chart engine still seems to be a bit buggy. For example, if you use dynamic named ranges as source data for your chart, the names should not begin with 'chart' or you will have problems. There are also a few issues with complicated defined names (e.g. if your defined name is a complex formula) in charts. I would try and get hold of a backup copy of Excel 2003 if at all possible for those times when things go wrong for no apparent reason and you have a deadline to meet. :)