N
Noel
Hi. I posted about this recently and actually managed to
find a way of recovering the sitation but Im still having
problems and I wonder if anyone has any views.
Im using Access 2003 on XP, in a networked environment.
Just over a week ago, while exporting some objects from a
copy to the main db, I get a strange message about a
record having lost its key index. When I OK this, the
next message says Record Deleted. Then I cant get rid of
the message by OKing it, and cant close the database. So
I do a ctrl alt delete and do an End Task. This closes
the database and when I reopen it, I get a message saying
the file I tried to open is corrupt. If I repeatedly
click on OK, the db does open at the Tab Form I have set
to open on startup. If I change startup to stop this form
opening, close the db, then reopen it, I dont get the
corruption message and can export tables but not any
other type of object. Being able to export tables saved
my bacon the first time this happened - because it was
the target (good) db that corrupted that time.
Since then Im getting random Disk or Network Error
messages and also, for no apparent reason, the cycle
described above happens. Sometimes this is when Im saving
an object Ive been working on, other times its when Im
exporting. I also got an error message about Automation
today - I couldnt get a command button to open a report.
The screen just flickered and stayed exactly where it was
(although other buttons did work). I closed down,
reopened again and it was OK. Once I was in a report in
design view, having a chat with a colleague and the first
error message just appears out of the blue. Mainly
though, the problem occurs when Im exporting stuff. I now
make sure I take a copy of the working db just before I
export, so its not longer a big disaster. (Good practice
any, I know). But when it does happen, I usually loose
what Ive been working on and have to redo it.
I know you will say - dont work in a backup and copy
objects across. OK there are better ways, but this never
gave me a problem before and it should work.
I must admit to not having done a compact and repair
before the first occurrance of this. But I have now done
this and its still happening. Any ideas? Is this likely
to be a network problem? Certainly the error messages
seem to be unrelated to what Im actually doing at the
time. The working db is unaffected by this - it continues
to work perfectly. But Im worried.
I would be interested in any views you have. Thanks, Noel
find a way of recovering the sitation but Im still having
problems and I wonder if anyone has any views.
Im using Access 2003 on XP, in a networked environment.
Just over a week ago, while exporting some objects from a
copy to the main db, I get a strange message about a
record having lost its key index. When I OK this, the
next message says Record Deleted. Then I cant get rid of
the message by OKing it, and cant close the database. So
I do a ctrl alt delete and do an End Task. This closes
the database and when I reopen it, I get a message saying
the file I tried to open is corrupt. If I repeatedly
click on OK, the db does open at the Tab Form I have set
to open on startup. If I change startup to stop this form
opening, close the db, then reopen it, I dont get the
corruption message and can export tables but not any
other type of object. Being able to export tables saved
my bacon the first time this happened - because it was
the target (good) db that corrupted that time.
Since then Im getting random Disk or Network Error
messages and also, for no apparent reason, the cycle
described above happens. Sometimes this is when Im saving
an object Ive been working on, other times its when Im
exporting. I also got an error message about Automation
today - I couldnt get a command button to open a report.
The screen just flickered and stayed exactly where it was
(although other buttons did work). I closed down,
reopened again and it was OK. Once I was in a report in
design view, having a chat with a colleague and the first
error message just appears out of the blue. Mainly
though, the problem occurs when Im exporting stuff. I now
make sure I take a copy of the working db just before I
export, so its not longer a big disaster. (Good practice
any, I know). But when it does happen, I usually loose
what Ive been working on and have to redo it.
I know you will say - dont work in a backup and copy
objects across. OK there are better ways, but this never
gave me a problem before and it should work.
I must admit to not having done a compact and repair
before the first occurrance of this. But I have now done
this and its still happening. Any ideas? Is this likely
to be a network problem? Certainly the error messages
seem to be unrelated to what Im actually doing at the
time. The working db is unaffected by this - it continues
to work perfectly. But Im worried.
I would be interested in any views you have. Thanks, Noel