![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
In my split dabase, which is used by 15 persons, the backend's main table suddenly misses 4000 records in comparison to last night's backup. I have never seen this before. I checked for corruption but didn't find anything. I repaired the db but no change. The missing records seem to be deleted randomly, I analysed the missing records but can't find a deletion pattern. Maybe a user went into the backend and did a deletion by accident. Has anyone experienced something like the above? Any ideas what could have caused it? Thanks, Martin |
#3
| |||
| |||
|
|
In my split dabase, which is used by 15 persons, the backend's main table suddenly misses 4000 records in comparison to last night's backup. I have never seen this before. I checked for corruption but didn't find anything. I repaired the db but no change. The missing records seem to be deleted randomly, I analysed the missing records but can't find a deletion pattern. Maybe a user went into the backend and did a deletion by accident. Has anyone experienced something like the above? Any ideas what could have caused it? Thanks, Martin |
#4
| |||
| |||
|
|
Thanks for your reply Bob. Good idea to put effort into preventing users gettting into the backend. Martin "Bob Darlington" schreef in bericht news:4de41fdc$0$22470$afc38c87 (AT) news (DOT) optusnet.com.au... martin (AT) hotmail (DOT) com> wrote in message news:6e633$4de39543$5356be6c$9358 (AT) cache110 (DOT) multikabel.net... In my split dabase, which is used by 15 persons, the backend's main table suddenly misses 4000 records in comparison to last night's backup. I have never seen this before. I checked for corruption but didn't find anything. I repaired the db but no change. The missing records seem to be deleted randomly, I analysed the missing records but can't find a deletion pattern. Maybe a user went into the backend and did a deletion by accident. Has anyone experienced something like the above? Any ideas what could have caused it? Thanks, Martin Martin. Unless you have a query or procedure in the front end which deletes records, I think that your suggestion that a user has accessed the backend is most likely. I recall posting a similar message here some years ago, and no one could come up with another answer. I try to prevent users from accessing the backend for this type of reason. Having said that, it probably wouldn't stop a determined 'sabateur'. -- Bob Darlington Brisbane |
#5
| |||
| |||
|
|
Thanks for your reply Bob. Good idea to put effort into preventing users gettting into the backend. Martin "Bob Darlington" schreef in bericht news:4de41fdc$0$22470$afc38c87 (AT) news (DOT) optusnet.com.au... martin (AT) hotmail (DOT) com> wrote in message news:6e633$4de39543$5356be6c$9358 (AT) cache110 (DOT) multikabel.net... In my split dabase, which is used by 15 persons, the backend's main table suddenly misses 4000 records in comparison to last night's backup. I have never seen this before. I checked for corruption but didn't find anything. I repaired the db but no change. The missing records seem to be deleted randomly, I analysed the missing records but can't find a deletion pattern. Maybe a user went into the backend and did a deletion by accident. Has anyone experienced something like the above? Any ideas what could have caused it? Thanks, Martin Martin. Unless you have a query or procedure in the front end which deletes records, I think that your suggestion that a user has accessed the backend is most likely. I recall posting a similar message here some years ago, and no one could come up with another answer. I try to prevent users from accessing the backend for this type of reason. Having said that, it probably wouldn't stop a determined 'sabateur'. -- Bob Darlington Brisbane |
![]() |
| Thread Tools | |
| Display Modes | |
| |