Microsoft Access won't open the database tables or forms

[Welshgasman]

Silly question, how do I go about setting this up?

Easiest and quickest solution is to change the shortcut so that it copies a MASTER copy of the FE (preferably in an .accde format) to the common location on the user's PC. Then runs access on that file.

I used to use a versioning process, so the user FE was only updated on new versions. Little more work for that to happen.

[CJ_London]

There are many ways and plenty of examples out there. Since we don't know your actual setup and any restrictions your IT dept may have you'll have to investigate which works best for you. Just google 'access vba how to distribute FE to users'. One of the links it should pick up is this one

https://www.devhut.net/ms-access-dep...to-your-users/

edit: In my FE I have code that runs on first open to check where it is and what it is called (currentdb.name). If either parts are incorrect for a user, it closes with a brief message explaining why. I tend to put the FE in the (usually hidden) users appdata/local/AccessFEs folder (create the last folder) and place a shortcut on the users desktop to the file. This prevents users from opening the FE on the shared drive or moving it around to another location on their machine - so you as developer know exactly where the FE is being run from if they experience errors.

One of my clients uses a folder C:\Databases on each users machine and their IT dept has set up a routine to run when the user logs in to automatically move a copy of the master on the server to this folder.

[newVBM3]

Easiest and quickest solution is to change the shortcut so that it copies a MASTER copy of the FE (preferably in an .accde format) to the common location on the user's PC. Then runs access on that file.

I used to use a versioning process, so the user FE was only updated on new versions. Little more work for that to happen.

If I go: File --> Save As --> Access Database(*.accdb).
Would it be the same as saving the FE to a users local machine and no longer messing with the master FE?

[Welshgasman]

Personally I would not give anyone an .accdb unless they were also going to develop it.
How are you going to implement changes then? You need a master and if you are going to do as you say above, you have to do that for every user, every time?

I am sure your time could be spent better elsewhere?

I would use Make ACCDE in Database Tools (at least that is where it is in 2007). Then give them that.

If you want to try a versioning method then have a look at
https://www.devhut.net/ms-access-dep...to-your-users/

@Vlad also has a method here https://forestbyte.com/ms-access-uti...a-db-launcher/

[newVBM3]

Personally I would not give anyone an .accdb unless they were also going to develop it.
How are you going to implement changes then? You need a master and if you are going to do as you say above, you have to do that for every user, every time?

I am sure your time could be spent better elsewhere?

I would use Make ACCDE in Database Tools (at least that is where it is in 2007). Then give them that.

If you want to try a versioning method then have a look at
https://www.devhut.net/ms-access-dep...to-your-users/

@Vlad also has a method here https://forestbyte.com/ms-access-uti...a-db-launcher/

No one else would be doing any development.
All they need to do is view tables, update info on the tables like quantity changes for orders, and queries. That is it.

The option is there for this version as well.

[CJ_London]

If I go: File --> Save As --> Access Database(*.accdb).
Would it be the same as saving the FE to a users local machine and no longer messing with the master FE?

I very much doubt you have access to other users machines to be able to do this

[newVBM3]

I very much doubt you have access to other users machines to be able to do this

That is not something for you to really worry about. But good point overall.
I do. I use screen share and request control.
And already done all users.

I am looking for best approach to this so that the DB doesn't get corrupted. If it does, it will now be just that persons computer and not domino effect.
Saving them locally seems to do the trick. The issue potentially could be if I add a new query or table, all users would not get the update.
If they need it, I can meet with them to add the table or query.

[Welshgasman]

You do not add the table or query. You just give the A copy of the master FE. A simple file copy.

[newVBM3]

You do not add the table or query. You just give the A copy of the master FE. A simple file copy.

That is correct, thanks for the correction.

[Bulzie]

Yes i have an exe users run that copies the latest version of the FE database down to their harddrive and then opens it there (backend is usually SQL). That way I can make any updates to the FE program and the next time they log in they will get the latest updates. If I need them to have the update right then, I just email them to log out and log back in(using Icon) and then they get the updated FE right then. I think there is examples of ways to do it on this site if you are interested in an automated process.