Upgrading some users to Office XP - will it hurt?

  • Thread starter Thread starter M Skabialka
  • Start date Start date
M

M Skabialka

I have about 50 people who use a FE/BE Access 2000 database, about half in
the same state, others all over the country. One group is going to upgrade
their PCs to Office XP; everyone is worried about how this will affect the
data.

Each person copies the FE to their own PC. The tables will stay in Access
2000 until everyone has upgraded.

When we went from Access 97 to 2000 everyone did it at the same time.

What pitfalls are there to upgrading some people to Access XP (2002? 2003?)?
Any horror stories so I can learn from this and we won't have any problems?

Thanks,
Mich
 
if you upgrade your office on one of the computers and see if it is working fine, if it does then do it on the other computers, be sure that your computer meets the minmum system requirement.
 
I have about 50 people who use a FE/BE Access 2000 database, about half in
the same state, others all over the country

This is the much bigger concern....you are using Access over a WAN? Just
asking for data corruption, unless you have the most stable connections in
the history of telecom. :-)

--
Kevin3NF

Sick of all that junk filling up your mailbox?
http://spamarrest.com/affl?2967001
 
Access XP and Access 2003 will run access 2000, XP etc but they won't run
Access 97 db's.

So if you have already migrated from 97 then I would roll out XP or 2003 or
2000 and keep the database format at Access 2000. This way Access 2000,
XP and 2003 clients can use it...

The version of Jet used by 97 is not as picky as the later ones. You MAY
encounter some strange problems in some forms if you overlooked something
minor in 97. But it won't be a big deal, just fix them as they arise.
 
Yes we are using it over a WAN - will it be less stable than with Access
2000? We make nightly backups, and have only lost data once when the server
filled up.

Mich
 
Access is prone to corrupting records when network connectivity is lost,
such as a glitch in a DSL or T1 connection, or even a bad NIC on a LAN.

I don't sell WAN based Access databases for this very reason.

Is your setup using the standard MDB FE and BE, or something else?

--
Kevin3NF

Sick of all that junk filling up your mailbox?
http://spamarrest.com/affl?2967001
 
FE on user machines, BE on a server.

I use the IP address to link the tables becuase we couldn't find a common
available drive letter for the FE to link to the BE becuase people are
scattered all over.

I am hoping users will remain on Access 2000 for now, but how different is
Access XP and what changes could it cause that might be problems?
 
Back
Top