Question about moving secured database to shared folder.

[Remedial]

My friends, today I have learned to dangers of securing your databases before placing them in their final destination. So, here's my question:

If I created a split database on my computer using an .mdw file that is on my network location, when moving this database to a public folder, would I have to move a copy of the .mdw file along with it in order for the database to be functional for others attempting to utilize this database?

I'm figuring that since the other users will not be able to access the .mdw file on my computer, I either have to create a new .mdw file for both portions of my database or move a copy of the original .mdw into the new location.

Am I correct?

 

[Alisa]

You should put the front end of your database, along with the mdw file, on each user's computer. Only the back end should go on the network.

 

[Remedial]

You should put the front end of your database, along with the mdw file, on each user's computer. Only the back end should go on the network.

I'll give this a try. Thanks.

But, when I do move the mdw file, do I have to change the workgroup file to the new location of the mdw file?

Also, will I have to relink the tables for every user that moves the front end to their computer?

Thanks again.

 

[Remedial]

I'll give this a try. Thanks.

But, when I do move the mdw file, do I have to change the workgroup file to the new location of the mdw file?

Also, will I have to relink the tables for every user that moves the front end to their computer?

Thanks again.

So, I had to create a whole new database after my last one got wrecked. I also learned that any security features that I enabled on the database are lost upon transferral to another users computer on the network. So, this is what I want to try: I'm not even sure about creating individual users and groups because I just intend to hand everyone the same front end. Also, trying to utilize that system the last time I tried sharing a database was totally ineffective. I don't think I'll be password protecting or encrypting the database (unless you guys think this is ultimately necessary). So, other than separating the database into a front end and back end and moving the workgroup file to each users computer (I'm pretty sure that I have to change the active workgroup to the new location of the workgroup on their computers), is there anything else that is necessary? Please help me out here, guys.

 

[Alisa]

The security should not be affected by moving your database. You might have to relink the tables depending on how the network is set up. Just put the mdw file in the same folder with the database on the users computers.

 

[Remedial]

The security should not be affected by moving your database. You might have to relink the tables depending on how the network is set up. Just put the mdw file in the same folder with the database on the users computers.

So, can I only give the users the front end portion of the database or do I have to give them the backend also? Or can I leave that on a shared folder on the network and just relink all the tables? Thanks for the help.

 

[Alisa]

So, can I only give the users the front end portion of the database or do I have to give them the backend also? Or can I leave that on a shared folder on the network and just relink all the tables? Thanks for the help.

There are literally thousands of posts on this forum about splitting databases. But yes, you can just give them the frontend, leave the backend on the network, and relink all the tables.

 

[Remedial]

There are literally thousands of posts on this forum about splitting databases. But yes, you can just give them the frontend, leave the backend on the network, and relink all the tables.

Thank you for your help. Just to let you know, I do know how to split databases, it's just that I've encountered issues when moving the necessary parts to different locations other than its original location.

 

[Alisa]

Thank you for your help. Just to let you know, I do know how to split databases, it's just that I've encountered issues when moving the necessary parts to different locations other than its original location.

You are welcome. I was just pointing out that the issues you are having have been covered in many posts before, and lots of them have way better answers with more info than what I have said.