Ask a Question related to Microsoft Access, Design and Development.
-
Dustin #1
The File <dbname> isn't an MS Access file or is corrupted
I have a database that contains data used for testing
other software products. There is a main form that allows
users to select scenarios they want to test and a subform
shows the data fields used for testing. Users can then
copy and paste the data out and enter new data in to be
used as inputs for other tests.
There is no workgroup created for this database users just
open the file and start testing. Record locking is
enabled on the form to keep users from updating the same
record at the same time. However there have been multiple
instances when multiple people are in the database that
the get the following error:
"The File <dbname> isn't an MS Access file or is corrupted"
Does anyone know what is causing this and what the remedy
may be? There is not a linked or embedded image on the
form or in the DB so I know it isn't that.
Thanks
Dustin
Dustin Guest
-
Checking if a file is corrupted
Object: AxAcroPDFLib.AxAcroPDF Language: C# How can I determine if a file is corrupted prior to calling LoadFile(...)? Or, how can I trap any... -
Contribute key file corrupted
When creating a Contribute key for a site hosted on a remote server, it timed out and advised that the file was corrupted. Apparently, I need to... -
corrupted dir file
I've created a director project with an external linked parent script. this script contains (like every parent script) an "on new" function. the... -
Recovery Of Corrupted File
My Mac crashed while I was working on my database and the file I was working on seems to be corrupted. I have tried the Recover option but I get... -
HELP!!!!! Corrupted log file
I have a corrupted active log file and my Database will not start. Is there anything I can do to force the database backup, i.e. ignore the... -
John Vinson #2
Re: The File <dbname> isn't an MS Access file or is corrupted
On Mon, 30 Jun 2003 10:01:27 -0700, "Dustin"
<rogedog@NOhotmailSPAM.com> wrote:
Just what it says: the file is corrupted so badly that Access can't>"The File <dbname> isn't an MS Access file or is corrupted"
even recgonize it as a database.
There are many ways whereby a database can be corrupted - one reason
why current backups are absolutely essential!
Among the common ones:
- Users interrupting Access by rebooting or by ctrl-alt-del and
stopping the Access program. Solution: carefully train users that
shutting off Access while it's running, other than by a decorous Close
process, is about like shutting off all three engines of a Boeing727
at cruising altitude. It's gonna crash unless you're VERY lucky.
- Bad NIC's or network noise. Solution: get a network wizard to snoop
(intensively! Access is VERY demanding of network purity) and replace
all bad NIC's.
- Too many users sharing the same front end. Solution: Split the
database, give each user their own copy of the frontend on their own
machine, sharing only the tables in a backend.
There are other reasons, but if you can get around these three I
suspect you'll have an easier time of it!
John W. Vinson[MVP]
Come for live chats every Tuesday and Thursday
[url]http://go.compuserve.com/msdevapps?loc=us&access=public[/url]
John Vinson Guest



Reply With Quote

