[AccessD] Access Multi-User BE Problems

I would urge you to try to find the problem first.  IMO this is probably a network problem.  NIC's are the first suspect.  Start
checking the MDW to see who was logged on when it crashed.  If that doesn't work log users in and out of a log file in a seperate
mdb.  Usually this traces down to one or two users who have machine/OS/software problems.  Is the network TCPIP?  Look at the Hubs.
Are them dumb hubs or switched routers?  Database programs demand much higher quality than most other apps.

Tom


----- Original Message -----
From: "Myke Myers" <mmmtbig at bellsouth.net>
To: <AccessD at databaseadvisors.com>
Sent: Friday, January 24, 2003 1:23 PM
Subject: [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.