Having problems using Access database with virtual private networ

I work in a contact center that uses an Access database to enter information
on calls that we receive. We are currently trying to start having employees
work from home through a virtual private network. The problem is that the
database created by Access only allows one remote employee at a time to open
the database as it thinks that the several individuals trying to use the the
database is actually one person allowing and does not allow the remote
employees to all use the database at the same time.

Please describe the installation of your database.

Is it split into a front-end that is copied to every user's PC and a single
back-end on your LAN?

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"mamaspizo" wrote in message
...
I work in a contact center that uses an Access database to enter
information
on calls that we receive. We are currently trying to start having
employees
work from home through a virtual private network. The problem is that the
database created by Access only allows one remote employee at a time to
open
the database as it thinks that the several individuals trying to use the
the
database is actually one person allowing and does not allow the remote
employees to all use the database at the same time.

In addition to Jeff's questions about splitting the db, an Access database
will not work reliably over a VPN. Performance will generally be awful. Data
corruption is too likely to be worth the risk. The only reliable way to use
an Access db remotely is either Remote Desktop, where the remote user is
actually working on a local PC but connected to that pc over the VPN, or
Terminal Server which lets multiple users work on a single local server. In
both those cases all the db access is local, and just the keystrokes/mouse
movements and screen bits are transferred across the VPN.

Another option for remote access would be a web application, but that's a
new development project.

"Jeff Boyce" wrote in message
...
Please describe the installation of your database.

Is it split into a front-end that is copied to every user's PC and a
single back-end on your LAN?

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"mamaspizo" wrote in message
...
I work in a contact center that uses an Access database to enter
information
on calls that we receive. We are currently trying to start having
employees
work from home through a virtual private network. The problem is that the
database created by Access only allows one remote employee at a time to
open
the database as it thinks that the several individuals trying to use the
the
database is actually one person allowing and does not allow the remote
employees to all use the database at the same time.

On Mar 23, 6:23*pm, "Paul Shapiro"
wrote:

Another option for remote access would be a web application, but that's a
new development project.

That reminds me. Albert Kallal will be telecommuting a demonstration
of Access 2010's web capabilities at the Chicago Access User's Group
tomorrow evening. I will not be able to attend because the state BCA
pool championships start tomorrow evening. Personally, I cringe at
the idea of using Access to create websites, but I imagine that many
companies might be quite interested in doing that. Maybe I'll see the
light eventually. BTW, the group usually needs to be notified by 10
a.m. (Central Time) so that I.D.'s can be placed on a list to be
checked for access to the building for the meeting.

J. A. Fortune