Problems with a shared Access 97 DB

[DeanL]

Hi all,

I'm having a few problems with a shared access 97 db. I have the
database split with the tables on the server and everything else in
"client" front ends with links to the tables, e.g.
\\10.31.42.10\db\mydb.mdb but the whoever opens their front end first
appears to have exclusive access to the database. Anyone else who
tries to open the database can open it to a certain extent (as long as
the form in question has no data on it, e.g. the switchboard, splash
screen, etc.) but then gets the error 'Run Time error '3045' the file
is already in use' whenever someone tries to open any data bearing form
or query (or anything with data for that matter).

I've created several access applications that in some cases were
considerably more complex and in some cases less so similar to this in
the past with no problems and have followed the same procedures I
always have but to no avail. Everyone has the correct permissions to
the server as anyone can use the db but only one at a time.

I know this would always be more beneficial to create an application
like this in SQL Server but unfortunately, the company I'm creating
this for only has access 97 and that's it. So if anyone knows why this
may be occurring (sic) then I'd appreciate a little help.

Many thanks, D...

[Rick Brandt]

"DeanL" <de*************@yahoo.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...

Hi all,

I'm having a few problems with a shared access 97 db. I have the
database split with the tables on the server and everything else in
"client" front ends with links to the tables, e.g.
\\10.31.42.10\db\mydb.mdb but the whoever opens their front end first
appears to have exclusive access to the database. Anyone else who
tries to open the database can open it to a certain extent (as long as
the form in question has no data on it, e.g. the switchboard, splash
screen, etc.) but then gets the error 'Run Time error '3045' the file
is already in use' whenever someone tries to open any data bearing form
or query (or anything with data for that matter).

I've created several access applications that in some cases were
considerably more complex and in some cases less so similar to this in
the past with no problems and have followed the same procedures I
always have but to no avail. Everyone has the correct permissions to
the server as anyone can use the db but only one at a time.

And just what are those permissions? What you're describing sounds like they
don't have file create permission on the folder. Is an LDB file being created
when the first person opens the file?
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[DeanL]

Hi Rick,

Whoever opens the file seems to create a .LDB file (opening this in
notepad or the like shows the user name logged onto the database) but
no one else seems to be able to log in. There is another tables
database in the same location and there appears to be no problems
accessing this for the same people so it would appear to be my db only
that's having/causing the problem.

Thanks, Dean...

[salad]

DeanL wrote:

Hi Rick,

Whoever opens the file seems to create a .LDB file (opening this in
notepad or the like shows the user name logged onto the database) but
no one else seems to be able to log in. There is another tables
database in the same location and there appears to be no problems
accessing this for the same people so it would appear to be my db only
that's having/causing the problem.

Thanks, Dean...

Any possibility the shortcut has a /excl in it?

[DeanL]

It doesn't BUT, I seem to have got it working. It seems the clients
server is a UNIX box that they've been running Access DB's off for
years but they way it's set up is to stop direct access to the file and
only allow access through a link so once that link was created and the
Linked tables pointed to the link rather than the files directly it
seems to work fine (breath in deeply after such a long sentence). Many
thanks for your help guys and sorry to have bothered you with something
so trivial that I should have picked up myself.

All the best, Dean...

[David W. Fenton]

"DeanL" <de*************@yahoo.com> wrote in
news:11**********************@f14g2000cwb.googlegr oups.com:

It doesn't BUT, I seem to have got it working. It seems the
clients server is a UNIX box that they've been running Access DB's
off for years but they way it's set up is to stop direct access to
the file and only allow access through a link so once that link
was created and the Linked tables pointed to the link rather than
the files directly it seems to work fine (breath in deeply after
such a long sentence). Many thanks for your help guys and sorry
to have bothered you with something so trivial that I should have
picked up myself.

I would never under any circumstances put any of my clients' data on
a Linux file server. I would not support this.

It's not that Linux and Samba are not reliable -- they certainly are
-- it's that there are lots of complicated timing issues with the
way Jet works with the file system that I know for a fact is
supported by Windows, but can never know for certain what's going on
with Linux.

Linux and Access simply don't mix, in my opinion.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/