Users Receive Error, Kicked out of Access

One of my clients is having a problem where users will be kicked out
of an Access program. Six out of the seven users have an Access
runtime. The seventh user has Access 2003. The data lives on the
server in an Access database. All users have XP machines. Two of the
users seem to have the runtime location in Office10, the rest say
Office 11.

The problem occurred at least once in April, but almost daily in
October. Sometimes the message is "3046 - could not save; currently
locked by another user", other times they won't get an error number,
but will get the same message.

This program was written by someone else who has since passed away.
He used a workgroup file for security. Two of the users have read
only access. At one time I thought it was related to these users, but
that isn't always the case.

A few days ago I tried a compact and repair, but that did not help.
They said the system has slowed down. Some of the tables are quite
large. One table has 1.2 million records. Since I'm not completely
familiar with the program and it has to do with a County's taxes I am
reluctant to clean out files.

I have made sure all users have read/write privileges to where the
data and mdw live and on their local machine where their copy of the
program lives.

Once someone received the "could not save..." error all users seem to
see it on their screen even if they only had the program open, but
were not using it. Then they need to reboot their computer in order
to get back in. The strange thing is once it happens they seem to be
good for the day. I have checked at night to make sure people aren't
leaving the ldb open. Everything looks good.

I am hoping someone has some suggestions.

Thank you,

Jodi

Re: Users Receive Error, Kicked out of Access

Usually the "Currently locked by another user.." occurs in memo fields.
You'll see "#Error" in the memo field that is the locked record.

Compacting / repairing will not fix a locked record, you need Jetcomp.exe.
And you have to run jetcomp.exe until it comes up clean (usually 2 times
will do the trick). Try this link:

http://support.microsoft.com/kb/295334

Hope this helps,

Andy

Re: Users Receive Error, Kicked out of Access

Thank you for your suggestion. I'll try it tonight after everyone is
out.

I think it is strange, though, that after a reboot they are fine for
the rest of the day.

Jodi

Re: Users Receive Error, Kicked out of Access

That is strange. It depends what kind of record locking is in affect, I
would think. If it's page locking, then if they're in the vacinity of the
bad record, it could cause the trouble, whereas a reboot would clear the
lock. Just a guess...

Andy
wrote in message
news:1194370203.434770.18740@z24g2000prh.googlegroups.com...
> Thank you for your suggestion. I'll try it tonight after everyone is
> out.
>
> I think it is strange, though, that after a reboot they are fine for
> the rest of the day.
>
> Jodi
>
>

Re: Users Receive Error, Kicked out of Access

On Nov 5, 7:12 pm, j...@softwareplanning.com wrote:
> One of my clients is having a problem where users will be kicked out
> of an Access program. Six out of the seven users have an Access
> runtime. The seventh user has Access 2003. The data lives on the
> server in an Access database. All users have XP machines. Two of the
> users seem to have the runtime location in Office10, the rest say
> Office 11.
>
> The problem occurred at least once in April, but almost daily in
> October. Sometimes the message is "3046 - could not save; currently
> locked by another user", other times they won't get an error number,
> but will get the same message.
>
> This program was written by someone else who has since passed away.
> He used a workgroup file for security. Two of the users have read
> only access. At one time I thought it was related to these users, but
> that isn't always the case.
>
> A few days ago I tried a compact and repair, but that did not help.
> They said the system has slowed down. Some of the tables are quite
> large. One table has 1.2 million records. Since I'm not completely
> familiar with the program and it has to do with a County's taxes I am
> reluctant to clean out files.
>
> I have made sure all users have read/write privileges to where the
> data and mdw live and on their local machine where their copy of the
> program lives.
>
> Once someone received the "could not save..." error all users seem to
> see it on their screen even if they only had the program open, but
> were not using it. Then they need to reboot their computer in order
> to get back in. The strange thing is once it happens they seem to be
> good for the day. I have checked at night to make sure people aren't
> leaving the ldb open. Everything looks good.
>
> I am hoping someone has some suggestions.
>
> Thank you,
>
> Jodi

There are at least seven users. One table has 1.2 million records. The
data are important. The application's creator is dead. Things aren't
working so well.
I'll be surprised if a couple of "try this" responses here will solve
anything long term, although they might give temporary relief.
I suggest the people who are responsible for the work this database
does spend some money to upgrade or replace it.