You need to split the database, using a shared back end, and a separate
front end for each user. If that's a new concept, see:
Split your MDB file into data and application
at:
http://allenbrowne.com/ser-01.html
The object model has changed since A97. The old version used to save only
the objects that changed, but Access 2000 onwards uses a monolithic save
when you change the objects. In practice, this is not an issue if you split
the database (which is recommended for A97 anyway if you have multiple
users.)
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"alfredoag via AccessMonster.com" <u11123@uwe> wrote in message
news:7b73a1a3a223d@uwe...
> We have recently upgraded the MS Access 97 to MS Access 2003 in our PCs.
> When the PC were on Windows 2000 it was possible for several users to use
> the
> same data base (created in Access 97) at the same time.
>
> As we updated to Windows XP Pro, we were not able to do the same anymore
> (several users to use the same data base simultaneously).
>
> We converted the Access 97 databases to 2003, and still are not able to
> use
> them.
>
> The Database is storage in a Server (running Windows 2000 Server) to which
> we
> all connect using the same workgroup.
>
> Is there something that needs to be changed in Windows XP Pro to allow
> multi-
> users to the same database?
>
> Seems like Windows XP Pro is not allowing the users to access the database
> in
> a simultaneous manner.
>
> Is it because we are in workgroup? Is Windows XP, or the Server Version?