Re: Front End Back End Problems

• Previous message: dawn: "access locking problem"
• In reply to: Immanuel Sibero: "Re: Front End Back End Problems"
• Next in thread: Steven C: "Re: Front End Back End Problems"
• Reply: Steven C: "Re: Front End Back End Problems"
• Messages sorted by: [ date ] [ thread ]

Date: Thu, 1 Apr 2004 14:29:33 -0800

Hi Immanuel,
I gave this idea of updating the system.mdw file a try and
it did not help. I have narrowed down the problem to
being caused by four of our departments 12 computers.
Each of this have been setup or resetup since the middle
part of last summer by our IT Dept. all others were
updated to Windows 2000 about a year before that. Only
these four cause the lockouts to happen. The others can
work at the same time without problems. I have also
discovered it is affecting all of our split databases,
which is basicly all of our current databases. The front
ends are all located on local workstation drives and the
back ends are all on the same server. I have had IT check
out the server and there is no reported problems with it.

Thanks for all of your help.
Steven
>-----Original Message-----
>
>Hi Steven,
>
>The workgroup file is system.mdw. There may be multiple
system.mdw on a
>machine. To find out which one is being used in an Access
session, pull up
>VBA Editor (Ctrl-G) and the Immediate Window, type in:
>
>? Application.DBEngine.SystemDB
>
>This will tell you the location of the system.mdw in
effect. You can copy
>the default system.mdw from another machine since they
are all identical.
>
>HTH,
>Immanuel Sibero
>
>
>
>
><anonymous@discussions.microsoft.com> wrote in message
>news:16ce401c417f6$14098b60$a301280a@phx.gbl...
>> Hi Immanuel,
>> Thanks for the suggestions. I have already done most of
>> this. I am sure the problem is isolated to one
>> workstation causing it. I just can't figure out what is
>> different on it. The front ends are copies from an
>> original that is stored on the server. All the other
>> workstations seem to work together fine. I have a
>> temporary fix in that I have one of our laptops
operating
>> in place of the workstation that is causing the problem.
>> Everybody is recognized as admin and this is using the
>> default workgroup that comes with Access.
>>
>> Is it possible that this one work station may have a
>> different default workgroup. If so how do I check it or
>> replace it with one from the others.
>> Steven
>> >-----Original Message-----
>> >
>> >Hi Steven,
>> >
>> >I'm sure you've got this covered. I would also check
and
>> be sure that
>> >everyone has all rights (read, write, delete, modify)
on
>> the folder where
>> >the database is. And noone is actually opening the
>> database exclusively. You
>> >can also sort of "watch" the .ldb file and observe its
>> behavior and make
>> >sure it behaves as expected.
>> >
>> >For example, if noone is logged on to the database,
there
>> should never be an
>> >..ldb file. The first user gets on, an .ldb file has to
>> be created. If one
>> >user gets on and no .ldb file is created, then that
user
>> has the database
>> >open exclusively.
>> >
>> >
>> >HTH,
>> >Immanuel Sibero
>> >
>> >
>> >
>> >
>> >"Steven C" <anonymous@discussions.microsoft.com> wrote
in
>> message
>> >news:1374e01c41726$6cea3160$a601280a@phx.gbl...
>> >> Each user has there own front end. The primary
(daily)
>> >> data is stored in a back end data base. Reference
data
>> is
>> >> stored in a second back end data base (Updated
>> annually).
>> >> The problem started after some computers crashed
with a
>> >> virus last summer and were taken in by our IT dept.
and
>> >> reformated. It seem to straighten out for all
computers
>> >> except one. She could not work the same time anyone
else
>> >> was on this application. Then we upgrade a computer
and
>> >> moved the replacement over to an office that had an
even
>> >> older computer. This is when it really got serious
and
>> >> will most of the time only let one person at a time
in.
>> >> IT people and I have both been searching for what
>> changed
>> >> but have not found it. It is not consistent in what
it
>> >> does. Sometimes when we are trying to chase it down
we
>> can
>> >> have everyone in there frontends working find with no
>> >> lockouts. Can't ever figure out why the difference
>> >> between when it works and when it doesn't. (I hope
we
>> >> find it before I become bald from pulling out my
hair.)
>> >> Thanks for the lead.
>> >> Steven
>> >>
>> >> >-----Original Message-----
>> >> >
>> >> >Hi Steven,
>> >> >
>> >> >- Does each user have his/her own front end?
>> >> >- Might want to check the following site, if you
havent
>> >> already:
>> >> >
>> >> >http://www.granite.ab.ca/access/tipsindex.htm
>> >> >
>> >> >HTH,
>> >> >Immanuel Sibero
>> >> >
>> >> >
>> >> >
>> >> >"Steven C" <anonymous@discussions.microsoft.com>
wrote
>> in
>> >> message
>> >> >news:113cb01c41683$b304f570$a001280a@phx.gbl...
>> >> >> We have an Access db that we have been using for
>> several
>> >> >> years. Recently we are having problems with the
users
>> >> >> locking each other out of the tables. The
problem is
>> >> not
>> >> >> consistently there making it difficult to trace
down
>> a
>> >> >> cause. Can anyone suggest what I might need to be
>> >> looking
>> >> >> for?
>> >> >>
>> >> >> Prior to middle of last summer we did not have
this
>> >> >> problem. Even then it was not a frequent thing
but
>> now
>> >> is
>> >> >> most of the time. We basicly have 2 to 5 people
on
>> the
>> >> >> front ends at any one time. We could have as many
as
>> 10.
>> >> >>
>> >> >> Thanks,
>> >> >> Steven C
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>
>.
>

• Previous message: dawn: "access locking problem"
• In reply to: Immanuel Sibero: "Re: Front End Back End Problems"
• Next in thread: Steven C: "Re: Front End Back End Problems"
• Reply: Steven C: "Re: Front End Back End Problems"
• Messages sorted by: [ date ] [ thread ]