Access 2007 issues

[mlai08]

We have been using an Access 2003 database in a shared network drive where 4 - 5 users can use the database simultaneously. However, we now have a new user with Access 2007 and everytime when she exits from the system, she was asked to save a copy of the file. We ended up having a number of copies left on the shared drive. This is very confusing to say the least.

Can anyone tell me how I can get rid of the prompt and bypass the need to save a copy on exit for the 07 user? We only want everyone to just work on the original file.

I tried to help her to create a Tursted Location on the network path of the database and the save prompt no longer pops up but a copy was still saved automatically on the drive each time she closes the file.

 

[SOS]

Okay this is a big deal - when multiple users are using a database you NEED to split the database (frontend/backend) where the backend has only the tables and that is on the server and then a copy of the frontend is on EACH USER'S MACHINE. You do not run shared files in Access. It will do it but it is a BAD, BAD, BAD, BAD idea.

 

[mlai08]

Okay this is a big deal - when multiple users are using a database you NEED to split the database (frontend/backend) where the backend has only the tables and that is on the server and then a copy of the frontend is on EACH USER'S MACHINE. You do not run shared files in Access. It will do it but it is a BAD, BAD, BAD, BAD idea.

I do understand the benefits behind splitting the database into front & backend. I did not do that to save the trouble of having to install a copy of the frontend to each user's PC on different locations whenever there is design changes on the frontend. Most of the users are not computer literate and I can see the potential problems of asking them to update the frontend if required and redo the table links on their own.

I know this is not an idea situation but it works fine for us.

My question really is how can one does away with saving a copy of an Access file located in a network under a 2007 environment.

Thanks

 

[SOS]

I did not do that to save the trouble of having to install a copy of the frontend to each user's PC on different locations whenever there is design changes on the frontend.

Then let it automatically update (Bob Larson and Tony Toews both have some excellent auto update stuff available so you and your users can have it work flawlessly and without user intervention).

I know this is not an idea situation but it works fine for us.

It is not about an ideal situation. It is that you are now suffering the ill effects of your decision. How can I make this clearer.

It is NOT a question of IF you should split. It is a MUST if you want to avoid problems AND corruption. The problems include the very problem you are stating now. So, you NEED, I repeat, you NEED to do the split and have the frontends on EACH machine or else you will CONTINUE to suffer problems. Get it?

Read this and get more about it.

My question really is how can one does away with saving a copy of an Access file located in a network under a 2007 environment.

Do what I said and you won't have the problem. PERIOD!

 

[mlai08]

SOS, thanks for your guidance. I'll give it a try.

 

[SOS]

Also, make sure that the user has full read/write/delete privileges on the folder where the file is located.

And make sure you have all of the service packs installed for 2007 as there are some funky things in there that get fixed.

But the big thing is making sure that nobody is sharing a frontend file because that can easily get screwed up by different settings on their computers and of course it can lead to all sorts of things up to, and including, corrupting all of your data and your database files.

 

[mlai08]

Also, make sure that the user has full read/write/delete privileges on the folder where the file is located.

And make sure you have all of the service packs installed for 2007 as there are some funky things in there that get fixed.

But the big thing is making sure that nobody is sharing a frontend file because that can easily get screwed up by different settings on their computers and of course it can lead to all sorts of things up to, and including, corrupting all of your data and your database files.

Hi there,

I have run the Auto FE Updater provided by Tony Toews in the server folder pointing it to a MDE file to be used by other users. Just try to get it clear in my mind - do I have to save a copy of the MDE file for the first time in user's local PC first and then create an User Setup Email to install the Auto Update application in the same folder containing the MDE file on user's hard drive?

Thanks

 

[SOS]

I'm not all that familiar with Tony's tool. He does allow questions to be sent to him from his website, so you might do that. I do believe though that his tool has a mechanism for sending out an email with the initial load information.