MS Access Multiuser - Encountered Access Error

Author

Encountered Access Error

Tarlac

2005-09-07, 8:25 pm

What might be the cause of this error we encountered :
"You or another user may have unexpectedly quit MS Access while MS Access DB
was open. Do you want Microsoft access to attempt to repair the DB?"

We are on a multi -user environment with other users accesing using the VPN.
Appreciate any response.

Tarlac

2005-09-07, 8:25 pm

I guess my question should be how do we prevent this error from happening.
Thanks

"Tarlac" wrote:

> What might be the cause of this error we encountered :
> "You or another user may have unexpectedly quit MS Access while MS Access DB
> was open. Do you want Microsoft access to attempt to repair the DB?"
>
> We are on a multi -user environment with other users accesing using the VPN.
> Appreciate any response.

Larry Linson

2005-09-08, 3:24 am

"Tarlac" wrote

[color=darkred]
[color=darkred]
> I guess my question should be how
> do we prevent this error from happening.

Are the multiple users on a LAN? Does each of the multiple users have
his/her own copy of the front-end (queries, forms, reports, macros, modules,
local lookup tables) linked to tables in the back-end(tables, relationships,
and data)? The "other users" via VPN: are they using terminal services, and
does each have his/her own disk assigned, his/her own copy of the front end?
Could there have been network problems, like a dropped connection?

In multiuser environments, we observe that the probability of corruption is
significantly increased when multiple users are logged in to the same copy
of the front-end or to a monolithic database. The most frequently _proven_
causes of corruption in a multiuser LAN environment are all "ungraceful
termination": dropped connections, power outages, or users powering down
their machines while Access has an operation in progress. Avoid these by
improving network hardware and/or software, uninterruptable power supplies
for the whole network, and user education (in some instances that might mean
making "closing windows and shutting down the machine properly" a "condition
of continued employement").

The best collection that I have found of information and links on preventing
corruption in and improving performance in multiuser environments is at MVP
Tony Toews' site, http://www.granite.ab.ca/accsmstr.htm.

Larry Linson
Microsoft Access MVP

Tarlac

2005-09-09, 1:26 pm

Thanks Larry.
We just implemented our system on remote access. Currently , the DB is not
split yet but we plan to do it .
It used to run on LAN environment but now we have to connect our mobile
users.
What we did is house our access system on the corporate server, then mobile
users access it through VPN by dialing up at home . I am not so familiar with
networking, how does terminal services work for remote users? Do we need to
make changes in our Access system to make it terminal server ready? Also, do
we need to buy licenses for these terminal servers or is this a feature of
the Windows Server? I am quite interested as I think this will improve the
response time of our remote users.Aprpeciate your response.

"Larry Linson" wrote:

> "Tarlac" wrote
>
>
>
>
> Are the multiple users on a LAN? Does each of the multiple users have
> his/her own copy of the front-end (queries, forms, reports, macros, modules,
> local lookup tables) linked to tables in the back-end(tables, relationships,
> and data)? The "other users" via VPN: are they using terminal services, and
> does each have his/her own disk assigned, his/her own copy of the front end?
> Could there have been network problems, like a dropped connection?
>
> In multiuser environments, we observe that the probability of corruption is
> significantly increased when multiple users are logged in to the same copy
> of the front-end or to a monolithic database. The most frequently _proven_
> causes of corruption in a multiuser LAN environment are all "ungraceful
> termination": dropped connections, power outages, or users powering down
> their machines while Access has an operation in progress. Avoid these by
> improving network hardware and/or software, uninterruptable power supplies
> for the whole network, and user education (in some instances that might mean
> making "closing windows and shutting down the machine properly" a "condition
> of continued employement").
>
> The best collection that I have found of information and links on preventing
> corruption in and improving performance in multiuser environments is at MVP
> Tony Toews' site, http://www.granite.ab.ca/accsmstr.htm.
>
> Larry Linson
> Microsoft Access MVP
>
>
>

Larry Linson

2005-09-10, 3:24 am

"Tarlac" wrote

> We just implemented our system on
> remote access. Currently , the DB is
> not split yet but we plan to do it .
> It used to run on LAN environment
> but now we have to connect our
> mobile users.
> What we did is house our access
> system on the corporate server, then
> mobile users access it through VPN
> by dialing up at home . I am not so
> familiar with networking, how does
> terminal services work for remote users?
> Do we need to make changes in our
> Access system to make it terminal server
> ready? Also, do we need to buy licenses
> for these terminal servers or is this a feature of
> the Windows Server? I am quite interested
> as I think this will improve the response
> time of our remote users.Aprpeciate
> your response.

Split the database, first thing. If your data is unsplit, and you have
multiple users logging in, then corruption won't only take down an easily
replaceable copy of the front end, it will take down your data. And, by
having multiple users logging in, you will significantly increase the
probability of corruption.

Using Terminal Services, the users' work is run on the server. With Access,
you need to ensure that each user has his own disk space and his own copy of
the Access front-end/client. As far as I know, the Access issues are no
different than other environments, with the exception that if the users are
running in the same machine with the data, retrieval will be at computer
internal speed, rather than LAN speeds.

I don't have answers to your licensing questions. I have heard that each
user requires an Access license, that each user requred a Client Access
License, but I am uncertain if an additional license per user of Terminal
Server is needed.

Larry Linson
Microsoft Access MVP

Sponsored Links