Access 2000 vs 2003

  • Thread starter Thread starter Ron Boetger
  • Start date Start date
R

Ron Boetger

Is there a Data base file format change between Access 2000 & 2003?

I have a customer that just purchased a new computer that came with
Office 2003 pro. There other computers are running Office 2000 Pro.
They share the Access database. The fellow using the new computer
says he expirenceing strange things using Access 2003 when he opens
the shared data base created with Access 2000.

Thanks

Ron
 
The two other computers are running Windows 2000 & MS Office 2000 Pro.
The new computer is running Win XP & Office 2003. It is acting as the
server for the other two computers. The Access 2000 database resides
on the new XP computer.

The fellow that sits at the new computer has created forms that are
only for him. He is trying to hide them from the other users. He
says his Access is running slow and kludge.

Any Ideas or suggestions would be appreciated.

Thanks

Ron
 
Ron Boetger said:
The two other computers are running Windows 2000 & MS Office 2000 Pro.
The new computer is running Win XP & Office 2003. It is acting as the
server for the other two computers. The Access 2000 database resides
on the new XP computer.

The fellow that sits at the new computer has created forms that are
only for him. He is trying to hide them from the other users. He
says his Access is running slow and kludge.
Click to expand...

One possible slowdown is that is Access installation may have the Name
AutoCorrect option turned on. I'd suggest he turn it off. Working with
Access 2002, I normally turn it off completely, but I think (from what
I've read) that some of the features of Access 2003 -- such as the
ability to find dependent objects -- require that the "Track name
AutoCorrect info" option be turned on, even if you don't turn on
"Perform name AutoCorrect".

Since I'm now working with A2003, I haven't decided whether I would turn
on any part of Name AutoCorrect just to get access to those features.

Is everybody using the same, unsplit database, with multiple users
working in that one database file at the same time? That setup is
susceptible to corruption and not recommended.
 
Back
Top