Read-Only Mode ACCESS 2007

[mapat]

Hello,

I have ACCESS 2007 (fe) linked to SQL Server 2008 (be). Currently, all the users have the front end on their local drives and that's what they work with. I want to have a main front end on the server and give the users a shortcut to that same front end, so everytime I have to modify the front end I don't have to do it individually (for every user). The problem is that when I do this and I click the shortcut from my computer and then open it from another user's PC, the front end opens in read-only mode on that other PC. Why is this and is there a way to get rid of it??

Thanks

 

[ghudson]

Each user should have their own front end on their computer [linked to a shared backend] that they use in a multi-user database. Users should not share the same front end file. You just need to figure out how to update the users local copy of the front end each time you have an update to push. Search around for there are many variations on how to do it to meet your needs.

 

[mapat]

Is there a particular reason why this should be done like that?

 

[vbaInet]

To reiterate ghudson's point, if your users are sharing the same front-end then access will disable the features that will enabled you modify the design. Imagine pulling out your steering wheel whilst the car is in motion You can guess what could possibly ensue.

There are so many advantages to ghudson's suggestions. Have a quick search.

 

[boblarson]

And if you want an automated way to keep their frontends updated, you can look at my free auto update enabling tool (at the link in my signature) or look for Tony Toews' Auto Updater.

 

[Sangie]

This is one of the first things I had to take on when I started working on databases. I have this same set up with a few of our bigger databases. I have the SQL Server backend and the frontend for data entry is in a shared folder on our network server. The end users all have a shortcut that points to this same frontend and they sign on with their own usernames and passwords.

When I need to work on anything, I have a copied fe & a shortcut that links to that copied fe. Then when the update is ready, I just tell everyone to sign off and I replace the frontend with the new one.

Are all your users permissions as Full Data Users or are they Read-Only Users?

 

[vbaInet]

This is one of the first things I had to take on when I started working on databases. I have this same set up with a few of our bigger databases. I have the SQL Server backend and the frontend for data entry is in a shared folder on our network server. The end users all have a shortcut that points to this same frontend and they sign on with their own usernames and passwords.

When I need to work on anything, I have a copied fe & a shortcut that links to that copied fe. Then when the update is ready, I just tell everyone to sign off and I replace the frontend with the new one.

Are all your users permissions as Full Data Users or are they Read-Only Users?

Still not an effecient way of handling it. What would happen if a user goes to the target of the shortcut and deletes it by mistake?

It's inconveniencing (to say the least), shortcuts could go amis, relinking could turnout to be a mess, corruption of your front end etc... the list goes on.

 

[Sangie]

Still not an effecient way of handling it. What would happen if a user goes to the target of the shortcut and deletes it by mistake?

It's inconveniencing (to say the least), shortcuts could go amis, relinking could turnout to be a mess, corruption of your front end etc... the list goes on.

Very true....we actually have trustee rights set up for the shared database folders as well as a Filer recovery software incase someone happens to delete a file on accident or one that they weren't supposed to....so if you don't have that set up, I wouldn't recommend the setup we have.