Access 2007 cannot open DB on LAN

[Shoregeek]

Hello.

I have a client with several machines on a LAN (their office) all running
Windows XP Pro SP2. Most of the machines are running Access 2003, however
one machine is running Access 2007.

The machine that is running Access 2007 can never access the network-stored
database if anyone else is already in it. However, if the Access 2007
machine is logged into the database first, everyone else can log in without
issue.

Hope someone in here can suggest something to aid in this problem.

Thanks!
Shoregeek

 

[Shoregeek]

Ah, OK. I haven't worked in Access for a long time, so I'll have to tinker
with that a little bit.

Thank you very much!

 

[Shoregeek]

Question. Within the database that everyone in this office is trying to
access, usually at the same time, they are all typically accessing the same
table.

Will this splitting of the database still let everyone access the specific
table? Or do we need to do something fancy?

Thanks!

 

[a a r o n . k e m p f]

Access is not strong enough to support multiple locks on the same
table.

SQL Server supports real locking.

Access does not.

SQL Server is free.. you should have upsized a long long long time
ago.

 

[Shoregeek]

If databases were my specialty, then perhaps I would have moved to SQL the
first time I met this client. Given that I am not a database person, I
don't think I should be beaten down for a client not having moved to a
platform I am sure they know nothing about.

Thanks for the information anyway.

 

[a a r o n . k e m p f]

you're not any sort of person whatsoever.. if you don't do SQL Server

Access isn't reliable enough for a single record nor a single user.

 

[Tony Toews [MVP]]

Question. Within the database that everyone in this office is trying to
access, usually at the same time, they are all typically accessing the same
table.

Will this splitting of the database still let everyone access the specific
table? Or do we need to do something fancy?

Yes, that will work quite well.

Please ignore Aaron Kempf's postings as he is rather monomaniacal.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[a a r o n . k e m p f]

splitting isn't reliable.

sorry. upsize to SQL Server if you give a shit about your data
if you don't give a shit about your data-- keep it in excel

 

[zmickle]

Experts and books all say that you can share an Access back end on a shared
drive with the front end running on each host computer. I have a simple
database that tracks student data and it is shared between 4 staff memebers.
Each staff computer has a copy of the front-end (linked tables, forms, and
queries). They basically only use one form. The form works like this

Form -> Query -> Linked Tables -> Main DB Tables

When the user opens the form initially, it works just fine. In fact, two or
three users can open it up and edit fields simultaneously, but after an
update has been made, only those who have that form open can continue editing
(and it works fine). BUT, when the next user tries to open the form a
message in the lower left corner says "this recordset is not updatable". At
that point, the data is locked to any new users. Anyone who was already in
can access and update the data, but any new instances of the form are not
updatable.

I have double checked that the form and underlying query have "No Locks." I
have noticed, however, that for some arbitrary period of time the
"record-locking" file is created for the back-end databse, even when it's not
open.

Any help would be greatly appreciated. This has been the bain of my
existance for weeks.

Thanks,

Zmickle