[AccessD] What Causes Database Strange Behavior

If your users all use a shared front end written in A2k but open it with
different versions of Access, I'm not surprised you're getting some odd
results.  Give them individual front ends and save yourself some
headaches.


Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Hewson
Sent: Friday, July 21, 2006 5:33 AM
To: AccessD
Subject: [AccessD] What Causes Database Strange Behavior

A2K BE, users access it with A2K, AXP and A2003.
Both reside in the same directory on a common mapped network drive.
Usually there are two or three users accessing it at the same time...
rarely does the user count go above five.
 
Problem:  Yesterday, the database started closing without warning.
Bypassing the opening script the FE opens as expected.
Either opening the Main form or attempting to access the code, the
entire database would shut down.
 
I did a compact and repair (both FE and BE), I decompiled and
recompiled, nothing seemed to work.
I finally created a blank container and imported all objects and
relinked the tables.  It seems to be working correctly.
I have no idea why this happened.
 
What would cause this strange behavior?  
 
I would like to see if the old file can be fixed, as a learning tool, if
nothing else.
 
Thanks,
 
Jim
 
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com