Using different versions of access 2000 and 2003

[david_oboyle]

I keep getting the error saying the database needs to be repaired, and
get this 6-7 times per day

We have 15 people who access the database over a network, 10 people
using access 2000 and 5 people using access 2003


All users have admin privilages enabled and access the database through

1 file on a network


can the different versions be the cause of this problem? if not what
could this be


please help

 

[Guest]

Hi David,

Make sure that all users have the latest service packs installed for the
operating system, their copy of Office, and the JET database engine:

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528

1 file on a network

You need to split your database into two .mdb files: a front-end (FE) and
back-end (BE). For more information on this topic, please see the following
page:

Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Albert D.Kallal]

You need to split your database...else no reliability will exist...

I explain what this is all about here:

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

 

[Albert D.Kallal]

sorry...worong link...here

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[boyley]

So if we have 15 different access files on the users workstations,

how will the back end file be updated,

and can each user view all the information the database as normal

 

[Albert D.Kallal]

So if we have 15 different access files on the users workstations,

how will the back end file be updated,

If they are split...then each front end file will be linked to the back end.
That means any user who updates the data will be editing data in the back
end...

read the split article again...I talk about how you must be careful to link
the Front end to the correct back end.....

and can each user view all the information the database as normal

Yes, for the most part. Of course, when you start having that many
users...it makes sense to start hiding the ms-access interface, and building
them a nice application. You likely should keep users out of the table views
directly..as it is very easy to erase, or empty out a table (ctrl-a and then
a delete key will zap a lot of data. Really, very dangerous. ....

As for keep each machine updated, then you can use Tony's free auto updater
here...

http://www.granite.ab.ca/access/autofe.htm