I work in the IT dept at the local council. We have 600+ PC's all with Access 97 as a standard roll out to our XP workstations.
Due to a lack of support from Micro$oft on older products, we are forced to upgrade and the target platform is Access 2002 on XP.
The council has been using A97 for almost 6 years so any proposal I make to roll out Acess 2K2 needs to impact on as few mdb's as possible.
Has anyone done this before or can point me to a white paper on the common traps to watch out for. I've combed through MSDN and technet but couldn't find a nice compact "what works and what doesn't" document. The holy grail in migrations!
As a side note, can I opt to roll out MS Access 2k2 but leave the mdb's as 97 (yes - I know I can ) but somehow supress the "would you like to convert this database" screen that user's get when they access a 97 mdb?
This would make the migration far more palatable as the convertion of all our mdb's (a few hundred) would not be a precursor to our MS Access upgrade.
Due to a lack of support from Micro$oft on older products, we are forced to upgrade and the target platform is Access 2002 on XP.
The council has been using A97 for almost 6 years so any proposal I make to roll out Acess 2K2 needs to impact on as few mdb's as possible.
Has anyone done this before or can point me to a white paper on the common traps to watch out for. I've combed through MSDN and technet but couldn't find a nice compact "what works and what doesn't" document. The holy grail in migrations!
As a side note, can I opt to roll out MS Access 2k2 but leave the mdb's as 97 (yes - I know I can ) but somehow supress the "would you like to convert this database" screen that user's get when they access a 97 mdb?
This would make the migration far more palatable as the convertion of all our mdb's (a few hundred) would not be a precursor to our MS Access upgrade.
