Hi Jeff,
I've tried about everything and it's still getting corrupted.
Have you looked into possible hardware issues. The last part of the reply I
wrote on 10/14 includes the following:
"If corruption continues, especially from one individual, then it's time to
start checking out their personal practices (ie. proper exiting of the DB),
along with thier hardware. They may have a bad network interface card, or
some other problem in the network (network cable, router, etc.)."
Is the file server on a UPS (Uninterruptable Power Supply)? If you are in
an industrial environment, with motors that draw a lot of current when they
start, you could be getting voltage line sags that are enough to account for
this type of corruption. This would apply to your users as well. I know of
one case where a PC was plugged into the same circuit as a vending machine.
The database would get corrupted every time break time came around. As
employees were purchasing cans of pop from the vending machine, the voltage
sagged just enough to cause corruption in the JET database.
I thought maybe a wireless laptop was disconnecting from the network
and causing the database to corrupt.
You need to ask, beg, demand, etc. that people *never* open your database
with a wireless connection. This is an inherantly unstable setup. JET
databases are just not suitable in such an environment. If your users insist
on using wireless connectivity, then you need to insist on migrating the BE
database to SQL Server.
I hardwired the laptop and it still got corrupted.
It might have already been corrupted from the wireless activity.
I couldn't compile the code, the selection seemed grayed out. I also
don't have any modules, so I think your suggestion on adding Option Explicit
doesn't fit for my situation.
The selection will be greyed out if the code is already compiled. Are you
sure that you have absolutely no code behind any forms and reports? If you,
or someone previous, ever used the command button wizard to add a command
button to a form, then you more than likely have some VBA code in your
project. Create a new stand-alone module. While in the VBE (Visual Basic
Editor) environment, click on View > Project Explorer. Do you see any forms
or reports displayed? If so, these forms and reports have code modules
associated with them. They may very well be empty modules, in which case they
can be deleted.
As for the Uniform Naming Convention, I'm just pointing to the BE using
the linking in Access, I do not have drive letters hard coded.
The linked table manager uses hard-coded drive letters unless you navigate
through My Network Places. If you click on Tools > Database Utilities >
Linked Table Manager, and you see a drive letter specified at the beginning
of the path, then you are indeed using hard-coded drive letters.
Should I start messing with the record locking?
Not at this time. I would solve the corruption problem first.
If you can compact and zip a copy of your front-end and back-end files, and
send them to me, I will take a look at them for you. A slightly obfuscated
form of my e-mail address is shown below. It should have 18 characters total,
after you remove the indicated characters. Whatever you do, please do not
post your real e-mail address to any newsgroup message.
Tom
QWaos168@XScom cast. Dnet (<--Remove all capitalized letters and spaces).
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
:
Hi Tom,
I'm back, unfortunately without happy results. I'm about at my wits ends
with this database and am very frustrated. I've tried about everything and
it's still getting corrupted. My latest attemps have been that I've had one
desktop reimaged back to original thinking it could be a corrupted OS file
that was causing the mouse to corrupt the database. I thought maybe a
wireless laptop was disconnecting from the network and causing the database
to corrupt. I hardwired the laptop and it still got corrupted. This morning
I created a new database from scratch AGAIN and imported in the files as you
suggested earlier. This time I did not bring the main data back into it, I
only imported the structure, thinking that old data may be causing a problem.
I then did the best I could to follow your latest instructions. History on
this database, this was not my original database in the beginning, but I took
the original tables and created my own forms, queres, reports, macros, etc.
so I'm not sure if it was created in Access 97 or not. Data goes back to
2003, that's all I know. Because of that, I did your instructions on adding
the DAO 3.6 to the VBE. I got a little lost with your instructions from that
point. I couldn't compile the code, the selection seemed grayed out. I also
don't have any modules, so I think your suggestion on adding Option Explicit
doesn't fit for my situation. As for the Uniform Naming Convention, I'm just
pointing to the BE using the linking in Access, I do not have drive letters
hard coded. I did not make the front end a .mde file. I don't feel real
confident, after everything else I've done, that this will make the
difference for me.
Again, I'm very frustrated and am about to tell them to go back to paper and
pencil because this database going down once a day is making me look real bad
right about now and they're getting frustrated with the system and as a
result, me. Any other suggestions to try would be greatly appreciated. I
really don't know where to go from here with the exception of punting.
Should I start messing with the record locking? I currently have it set to
the defaults. Thanks.
