MultiUser and Multi Versions

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

TPG - 18 Feb 2005 02:53 GMT

Help - My networked (4 users for the past two years) database suddenly became
corrupted after I tried to connect to it through a new workstation that uses
Access 2003. All workstations are XP pro and access 2002. Server is a
utility linnux based server. The database itself is split having used the
splitter wizard. Do I need all workstations using the same version? If so,
am I better off biting the bullet and upsizing to SQL or MSDE??? Thanks!

Reply to this Message

Albert D. Kallal - 18 Feb 2005 11:32 GMT

I can't really say that using a2003 was (or should) be the problem.

Do note that a2003 and a2002 both use the SAME JET engine, and in fact by
default both a2002, and a2003 use the same file format.

> The database itself is split having used the
> splitter wizard.

You split the database. Are you ensuring that EACH workstation gets this FE
placed on EACH pc? (you M U S T do this to ensure reliable operation here).

> Do I need all workstations using the same version?

No, in fact, I had clients run access97, and access2003 hitting the same
back end data without trouble. So, by splitting, you can EASLEY run a mixed
environment, but you MUST as mentioned place the FE on each pc.

You should check the oplocks setting on the server side...and disable it...

Signature

Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.members.shaw.ca/AlbertKallal

Reply to this Message

TPG - 19 Feb 2005 12:41 GMT

Thank you - in fact, I have been placing both front end and back end on the
server. I'll change that immediately. Thanks again,
Tom Gorton

> I can't really say that using a2003 was (or should) be the problem.
>
[quoted text clipped - 14 lines]
>
> You should check the oplocks setting on the server side...and disable it...

Reply to this Message