A
Antonio
This was initially posted on the "General Discussions"
board on the 29th, but I have yet to get an answer to
all/some of my questions...I appreciate any thoughts.
TIA
Subject: Corrupt Database?
From: "Antonio" <[email protected]> Sent:
3/29/2004 8:02:04 PM
Please forgive the length of this posting; I have tried
to provide as many details as possible.
I have an Access Database that resides on a server that
is connected to all 20 of the workstations in my office.
4 of the workstations run XP while the others run Win
2000.
This database has simple VBA code running in one a module
called "Module 1" for all of its forms. It is not split
into a front and back end. The users access the database
through the User Level Security Wizard tool and has been
working rather well.
Since last thursday we have been having a problem that
has never occurred before.
Description:
1. Initially the user would open a form, place the mouse
cursor into a field, enter data, but nothing would occur
for approximately 3 seconds. Then an error message would
pop up saying (this is from memory), "Microsoft Access
has encountered a problem with the file MSACCESS.EXE.
Access will have to shut down and you will have to
restart the program." Then the user would get booted.
2. Since Sunday, the user would do the exact same thing
described above, but instead of getting the
above "Microsoft Access has encountered a problem
with...." message, a different, larger, error message
pops up stating,
"Microsoft Access has encountered a problem and needs to
close. We are sorry for the inconvenience.
The information you were working on might be lost.
Microsoft Access can try to compact and repair your open
database.
{yes} Repair my open database and restart Microsoft Access
Please tell microsoft about this problem.
We have created an error report that you can send to help
us improve Microsoft Access. We will treat this report as
confidential and anonymous."
Then I am given the option to see the error report. When
I choose this option a window pops up listing all kind of
data I dont understand.
"Error Signature-- AppName: msaccess.exe AppVer:
10.0.4302.0 ModName: unknown ModVer: 0.0.0.0 Offset:
01220688"
Then it lets me see the technical information associated
with the error, but I cant print it and I cant seem to
find anything that corresponds to my database in it.
Then Acess tries to compact and repair the database, but
it never works and gives me the following error messages:
"The command line you used to start Microsoft Access
contains an option that microsoft access does not
recognize. Exit and restart Microsoft Access using valid
command line options."
I click "OK" and the following message pops up:
"Microsoft Access cant find the database
file 'Access.mdb.' Make sure you enterd the correct path
and fild name."
However, I can log back in, go to tools, database
utilities, and manually compact and repair the database
with no problem...except that the error occurs 3 or 4
actions later.
I dont know what else to do. I switched it out with an
older back up copy but had the same problems. I did
notice the following things:
1. Each time this error occurs, when I go to the design
view of Module 1, I am always given the option to Compile
my project.(I click on "Debug", and "Compile Project 2")
When the database is fine, if I log off and log back on,
the compile option under the Debug is ghosted and I cant
do anything with it. When I do click on compile, it seems
to fix the database 90 percent of the time for a short
period of time.(sometimes minutes, sometimes an hour..one
time it was a whole day)
2. When I replaced the database with an older version in
the same folder on the server, the error was the same.
3. The lock files (2 of them, Secured.ldb and K2.0ldb)
seem to hang around. Normally they disappear when I log
off, but when this error occurs they hang out until I log
back in and log out...then they might disappear.
Sometimes the one lock file, that was created say 4 hours
ago will hang around and just go away by itself....
4. Just before these error messages occurred, I made very
minor changes to my database. (re structured queries,
changed some forms, added one sub routine to a forms on
open event, and thats it)
5. As I said before, the database is NOT split into a
front and back end. If I split it (the database that is
having these problems) how will my security files run?
Will I have to recreate them? Does the front end sit on
the server as well, and everyone's desk top short cuts
point to it?
6. Is it ever a problem having all the vba coding for a
database in one module? The module for this datase has 68
Microsoft Class Objects (all forms and reports). Each of
these class objects have anywhere from 1 to 60 seperate
sections of codes (Private Subs?) for the various buttons
and actions on the forms. Does it ever become a problem
that all this information is located in one module...can
a module ever get too big?
7. Can anything be gleamed from the technical error
report access generates that might help me? Is there a
resource an amateur can turn to that might help me
decipher such error messages?
I dont know what to do. This is an office wide database
that is in use by 30 people...they had to break out the
old paper logs from two years ago because of this. I
would really appreciate any help/suggestions anyone can
provide...
..
board on the 29th, but I have yet to get an answer to
all/some of my questions...I appreciate any thoughts.
TIA
Subject: Corrupt Database?
From: "Antonio" <[email protected]> Sent:
3/29/2004 8:02:04 PM
Please forgive the length of this posting; I have tried
to provide as many details as possible.
I have an Access Database that resides on a server that
is connected to all 20 of the workstations in my office.
4 of the workstations run XP while the others run Win
2000.
This database has simple VBA code running in one a module
called "Module 1" for all of its forms. It is not split
into a front and back end. The users access the database
through the User Level Security Wizard tool and has been
working rather well.
Since last thursday we have been having a problem that
has never occurred before.
Description:
1. Initially the user would open a form, place the mouse
cursor into a field, enter data, but nothing would occur
for approximately 3 seconds. Then an error message would
pop up saying (this is from memory), "Microsoft Access
has encountered a problem with the file MSACCESS.EXE.
Access will have to shut down and you will have to
restart the program." Then the user would get booted.
2. Since Sunday, the user would do the exact same thing
described above, but instead of getting the
above "Microsoft Access has encountered a problem
with...." message, a different, larger, error message
pops up stating,
"Microsoft Access has encountered a problem and needs to
close. We are sorry for the inconvenience.
The information you were working on might be lost.
Microsoft Access can try to compact and repair your open
database.
{yes} Repair my open database and restart Microsoft Access
Please tell microsoft about this problem.
We have created an error report that you can send to help
us improve Microsoft Access. We will treat this report as
confidential and anonymous."
Then I am given the option to see the error report. When
I choose this option a window pops up listing all kind of
data I dont understand.
"Error Signature-- AppName: msaccess.exe AppVer:
10.0.4302.0 ModName: unknown ModVer: 0.0.0.0 Offset:
01220688"
Then it lets me see the technical information associated
with the error, but I cant print it and I cant seem to
find anything that corresponds to my database in it.
Then Acess tries to compact and repair the database, but
it never works and gives me the following error messages:
"The command line you used to start Microsoft Access
contains an option that microsoft access does not
recognize. Exit and restart Microsoft Access using valid
command line options."
I click "OK" and the following message pops up:
"Microsoft Access cant find the database
file 'Access.mdb.' Make sure you enterd the correct path
and fild name."
However, I can log back in, go to tools, database
utilities, and manually compact and repair the database
with no problem...except that the error occurs 3 or 4
actions later.
I dont know what else to do. I switched it out with an
older back up copy but had the same problems. I did
notice the following things:
1. Each time this error occurs, when I go to the design
view of Module 1, I am always given the option to Compile
my project.(I click on "Debug", and "Compile Project 2")
When the database is fine, if I log off and log back on,
the compile option under the Debug is ghosted and I cant
do anything with it. When I do click on compile, it seems
to fix the database 90 percent of the time for a short
period of time.(sometimes minutes, sometimes an hour..one
time it was a whole day)
2. When I replaced the database with an older version in
the same folder on the server, the error was the same.
3. The lock files (2 of them, Secured.ldb and K2.0ldb)
seem to hang around. Normally they disappear when I log
off, but when this error occurs they hang out until I log
back in and log out...then they might disappear.
Sometimes the one lock file, that was created say 4 hours
ago will hang around and just go away by itself....
4. Just before these error messages occurred, I made very
minor changes to my database. (re structured queries,
changed some forms, added one sub routine to a forms on
open event, and thats it)
5. As I said before, the database is NOT split into a
front and back end. If I split it (the database that is
having these problems) how will my security files run?
Will I have to recreate them? Does the front end sit on
the server as well, and everyone's desk top short cuts
point to it?
6. Is it ever a problem having all the vba coding for a
database in one module? The module for this datase has 68
Microsoft Class Objects (all forms and reports). Each of
these class objects have anywhere from 1 to 60 seperate
sections of codes (Private Subs?) for the various buttons
and actions on the forms. Does it ever become a problem
that all this information is located in one module...can
a module ever get too big?
7. Can anything be gleamed from the technical error
report access generates that might help me? Is there a
resource an amateur can turn to that might help me
decipher such error messages?
I dont know what to do. This is an office wide database
that is in use by 30 people...they had to break out the
old paper logs from two years ago because of this. I
would really appreciate any help/suggestions anyone can
provide...
..