Corrupt DB?

[rkdcomp]

I have someone that is getting this message>

"another user are attempting to change data at the same time"

I know I'vee seen an answer to this someplace and for the life of me, can't find it.

Any help would be appericated.

Thanks,

Richard in Tulsa

 

[SonOfEmidec1100]

Make sure no one else is using the database then run repair & compact. Or just compact depends on the version.


cjw

 

[cohortq]

If it's still corrupt or you get wierd errors like "NETWORK PATH NOT FOUND" but you're accessing it off the network make a new database. Copy over all the tables, queries and macros over. With forms you need to make a new form, view them both in design view, copy over the form objects. If you have any back end code, view it in the code builder, copy it over to something like notepad, then copy it from there to the code builder in the new database. This may sound strange but believe me, the only way to get rid of all the corruptions is to do this. Code can easily be corrupted thats why you need to be careful with copying over forms and modules. Reports can also bring corruption with them for some crazy reason (it happened to me). You might need to re-create them. Ok I hope this helps.

 

[cohortq]

If it's still corrupt or you get wierd errors like "NETWORK PATH NOT FOUND" but you're accessing it off the network make a new database. Copy over all the tables, queries and macros over. With forms you need to make a new form, view them both in design view, copy over the form objects. If you have any back end code, view it in the code builder, copy it over to something like notepad, then copy it from there to the code builder in the new database. This may sound strange but believe me, the only way to get rid of all the corruptions is to do this. Code can easily be corrupted thats why you need to be careful with copying over forms and modules. Reports can also bring corruption with them for some crazy reason (it happened to me). You might need to re-create them. Ok I hope this helps.

 

[rkdcomp]

COHORTQ:

Now that you mentiond this procedure, it brings back thoughts of what sounds like what I ran into before.

Copying over the entire DB to a new clean DB.

I'll pass this on to my friend who is having the problem.

She is on a network, but was getting this when she was the only one using the DB.

Will post an answer if this solved the problem.

Thanks,

Richard in Tulsa.

 

[PaulaJ]

I have a data base that this occurs on a regular basis. Each time there is a record in the data base that has a value of #ERROR in one of the fields. I have to scan through the records (the Search won't find it) until I find the record and delete it. Then the DB works fine. I think that these records get corrupted when they are being displayed and the workstation freezes up, but that's just my opinion. Anyway, it's a lot easier than recreating the entire data base. Good Luck.