[AccessD] Message not deliverable

Administrator administrator at it.glasgow.gov.uk
Wed Jan 29 02:57:04 CST 2003


Myke,

all data traffic between frontend and backend is going over the network, so
I would doubt that splitting the backend would cause better performance.
But since your departments use distinct sets of tables you might be able to
track down an individual client machine that is causing problems.

AFAIK locking information is stored in the LDB-file that is created
automatically once someone uses a MDB-file. If you have multiple backends,
multiple LDB-files will be created. That might have influence on your
locking problems.

Database corruption can be caused by a crashing client machine or faulty
network connections. Since the server containing your backend db seems to be
pretty busy it might be worth moving the backend(s) to different machine.


Michael


-----Ursprungliche Nachricht-----
Von: AccessD-owner at databaseadvisors.com
[mailto:AccessD-owner at databaseadvisors.com]Im Auftrag von Myke Myers
Gesendet: Freitag, 24. Januar 2003 22:24
An: AccessD at databaseadvisors.com
Betreff: [AccessD] Access Multi-User BE Problems


I've developed an application for a corporate compliance dept that has
grown considerably in the last 4 years. There are about 25 users going
in and out all day. Only a few are entering data. The frontend app is on
the user's PC, with linked tables to the backend (BE). The BE is on a
busy server that handles many other applications. Several users are
coming in via a VPN.

This database gets locked up and/or corrupted about once a week. This
has become a significant problem. Migrating to Sql Server is in the
distant future, but I need to improve the situation now.

I'm thinking of breaking out the data tables in the BE database into
separate databases, grouped by departmental function. I would retain the
one frontend application.

I hope that this would increase responsiveness, reduce down time and
data corruption, and help us identify who/what is causing problems. At
least if one BE database gets corrupted, it wouldn't take out all the
users while it gets fixed.

Anyone have insight to share? Thanks in advance, Myke



This list sponsored by Database Advisors Inc., a worldwide association of
database developers.
Visit http://www.DatabaseAdvisors.com, the database developers' list portal
and support site.

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd



More information about the AccessD mailing list