Front end copies itself to desktop after closing db

[mafhobb]

I have a split db that has been in use for a few years by about 12 people. The front end is compiled into an accde file.

Ocasionally a user (randomly) might get an error message "Microsoft has detected that this database is in an inconsistent state...." when closing the db and when that happens, a copy of the front end is automatically placed on their desktop.

This front end is always deleted and the original front end continues to work just fine afterwards.

Why are my users getting this error message? Why is the front end automatically copied onto their desktops?

How can I avoid this?

Thanks

mafhobb

 

[Frothingslosh]

It sounds like you're having multiple users use the front end at the same time, which completely defeats the purpose of splitting the database in the first place.

Is that the case here? If so, just have everyone make and use a local copy and you should be good.

 

[RainLover]

If that is not the answer have a look at the default file locations.

They could have been played with by someone who shouldn't be touching things.

 

[fat controller]

I've had this happen with mine, and without exception it has been network issues that has caused the problem - - basically, the network drops mid-flow, then Access/Windows "decides" that there is something wrong and tries to backup to save your data....... only, the backup it creates is utterly useless nine times out of ten, and at the end of the day the data itself is protected as its in its own backend file.

Now, if you database wasn't split (as a few of mind used to be), this problem is the stuff of nightmares as you can easily lose everything when the network drops. If ever there was a reason to split a database, this is it.

 

[mafhobb]

Froshinglosh: The db is split and each user has its own front en. Sorry that I did not specify that.

Rainlover: I did not think about that possibility, but you are talking about the users messing with their own front end folder, right? They have no direct access to the back end on the network, only Access does.

Fat Controller: I see, so if this was the case, is there any way to check for network connectivity issues thorugh Access? I mean, if I could get Access to bring up a message when the network drops, it would be a lot easier to get the IT guys to look at it.

mafhobb

 

[mafhobb]

Does anyone know how to prevent access from copying itself on the desktop when it "sees" a network drop?

 

[fat controller]

Does anyone know how to prevent access from copying itself on the desktop when it "sees" a network drop?

Is your database split?

I had this happen with one of mine, but since splitting and ensuring that users have a copy of the front end saved on their PC (as opposed to accessing it on a network drive or via Citrix), I have had no more problems.