[AccessD] [SPAM SUSPECT] Re: What Causes Database Strange Behavior

Bobby Heid bheid at appdevgrp.com
Mon Jul 24 08:34:27 CDT 2006


Glad to hear you're going now.  I hate it when a bunch of things conspire
against me like that.

Bobby

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Hewson
Sent: Monday, July 24, 2006 9:07 AM
To: Access Developers discussion and problem solving
Subject: [SPAM SUSPECT] Re: [AccessD] What Causes Database Strange Behavior
Importance: Low


Thanks Charlotte and Bobby for responding.

Further investigation indicated that I was the only person having difficulty
with the database.  Most of the users had copied the front end to their
machines and were not having any problems.

I, on-the-other-hand, was having difficulty with several databases that were
not even remotely connected.  One database was using ODBC to SQL Server with
very few forms - and it was closing before I could get it open.  Regardless
of the version of Access I used to open them, they still would not function
correctly.

One database gave me an error message when I opened it up in A2K, then
wanted to know if I wanted to report it to Microsoft.  I finally (after
several attempts) reported it.  I was given KB article 323203:  ACC2000:
Access 2000 Unexpectedly Quits When You Run Code to Open an Object.
Essentially, it states the references need to be refreshed.  The other key
sentence was the CAUSE statement.  "The database was created in MS Access
2002, but the database is now in the Access 2000 File Format, and you are
working in Access 2000."  Refreshing the references helped some but did not
completely fix the problem.

In a whirlwind of activity trying to get this resolved, I was finally
directed to the Update site.  I did the Check for Office Updates and found I
needed several.  Some for each version of office I had on my machine.  I did
the updates and the problem went away...

Thanks.

Jim 
jhewson at karta.com
 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Friday, July 21, 2006 10:10 AM
To: Access Developers discussion and problem solving
Subject: Re: [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




More information about the AccessD mailing list