An issue with putting the backend of an Access database in a folder on a server and accdc issue

Hello All

Here is my situation.  I have created an Access database and will be putting the backend on a server that everyone will have access to.  Is there a way to allow each user to access the tables ONLY thru my front end of the program?  What I do not want a user to be able to do is open up the back end in a folder window and access the tables directly.

In a related issue, when I split the database it creates an accdc file.  I need to be able to add more tables to the back end and I am not sure how to work with an accdc file.

Thanks to everyone again!
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
You can password protect both the Frontend and Backend, but that won't stop someone who knows the password.

You could password protect, and then create a "launcher" app. The "launcher" app would open your password-protected app, and code would pass in the password (so the user does not need to know it). However, once it's open, users can use other apps to connect to it.

If you want true data security, switch to SQL Server and protect your data there. It has a very robust security system, and you can do just about anything you need.
Gustav BrockCIOCommented:
As for the accdc file, it is a signed package. That should not be needed. The backend file is usually an accdb file.
You should be able just to rename it to frontend_be.accdb, open the frontend, and run the relinker where you specify the new name of the backend file.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
alevin16Author Commented:
Thanks for the help!  I think we will move it to an SQL backend.  That would probably make the most sense.
Gustav BrockCIOCommented:
You are welcome!

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
You can get what you want by protecting the FE (distributing as a accde) and using folder security.

 What you do is place the BE in a subfolder of a data directory.   On the main data directory, you give users Traverse Folder rights only.  Might look like this:


 When they look in X:\appdata, they will see nothing but an empty directory, but can they can "jump over" \xyz32 to get to the data.  However they need to know the sub directory name.

So as long as you never expose the full path to the user in the app, then they can't get at the backend except through  the app (which knows the path).

But I agree with the others; SQL Server would be a far better choice if your concerned about security.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.