cannot distribute database to other computers

[complexx]

I created the database on my computer. I added security and split the database to put the tables on the the server. Everything works just fine on my computer. However, when I try to copy the 3 files for the front end of the database to other computers on the network, it won't work.

Perhaps I'm confused as to what files need to be migrated to each additional computer or I don't have the security setup properly.

Right now, I move 3 files. The main database file with the front end. The shortcut file that is created when you add security and the security file that is created when you add security to the database.

I'm stumped.

 

[The_Doc_Man]

Shared DB and Network Security

You are quite right that security could be your problem. Permit me to put on my "security professor" hat for a moment.

When you get the DB all set up and secured with the MDB file, you have half the battle done. The rest of the story, though, is to set up the network security. I'll assume you are not too familiar with this or you would have already done it.

What we did at our shop was to create a shared folder. For ease of operations, we made it close to the root of the shared drive. We didn't want too many folders between the drive and the final folder - it would have been that much more work to do for the folder settings.

Next we created a domain group for the database. All users of the DB were added to that group. The group conferred PASSTHRU rights for all users from the root through the (small number of) parent folders to the folder that held the DB files. We then set that folder and its child folders to allow nearly full access rights. Specifically, the folder needs to have just about every advanced permission except the ones that allow you to control the security of the folder itself.

You need to be able to create and delete files in that folder because of the .LDB file. You need to be able to read and update files in that folder because of the .MDB file. It is OK to propagate permissions down from the folder holding the DB and then go back to revoke "Delete" permission from the database file. But you DO need "Delete" permission on the folder because of the .LDB file.

Another thing to consider is whether everyone has the same drive letter configured for the database or whether you are using explicit node, drive, and folder paths. If user A maps to that drive as S and user B maps to the same drive as T, you got tsuris big-time. (If your Yiddish is not up to that word, it is "agony" or "pain.")

 

[complexx]

Trying to figure this out.

You are quite right that security could be your problem. Permit me to put on my "security professor" hat for a moment.

I would have prefered the lamens hat.

When you get the DB all set up and secured with the MDB file, you have half the battle done. The rest of the story, though, is to set up the network security. I'll assume you are not too familiar with this or you would have already done it.

No. I'm not familiar with it. Our network was "setup" (IMO, it was abandoned) prior to my first day of work by some "professional".

What we did at our shop was to create a shared folder. For ease of operations, we made it close to the root of the shared drive. We didn't want too many folders between the drive and the final folder - it would have been that much more work to do for the folder settings.

This part I have already done.

Next we created a domain group for the database. All users of the DB were added to that group. The group conferred PASSTHRU rights for all users from the root through the (small number of) parent folders to the folder that held the DB files. We then set that folder and its child folders to allow nearly full access rights. Specifically, the folder needs to have just about every advanced permission except the ones that allow you to control the security of the folder itself.

You need to be able to create and delete files in that folder because of the .LDB file. You need to be able to read and update files in that folder because of the .MDB file. It is OK to propagate permissions down from the folder holding the DB and then go back to revoke "Delete" permission from the database file. But you DO need "Delete" permission on the folder because of the .LDB file.

I understand what your saying and why your saying it, but would I know how to set this up? I don't think so. All I CAN say is that, after I split the database and moved the data files to the server in the shared folder, it worked fine. I was able to modify the data in the linked tables on my comptuer.

Another thing to consider is whether everyone has the same drive letter configured for the database or whether you are using explicit node, drive, and folder paths. If user A maps to that drive as S and user B maps to the same drive as T, you got tsuris big-time. (If your Yiddish is not up to that word, it is "agony" or "pain.")

All computers use the same drive letter to map to the shared folder.


What I cannot understand, is why the database functions properly using my computer and not any of the others on the network. This leads me to believe that it has less to do with network setup and more to do with the database security file information. Perhaps I need to specify to the database security file which computers will be accessing the database, etc. Or something along those lines. When I copy the same files I use for my front end over to other computers, those computers cannot even access the database using the secure link. Thats why I feel it has somethign to do with the way the security within the database is setup.

I can't stand this mishigas with the security. I'm open to suggestions.

 

[complexx]

I wanted to report on what happens when I try to open it on another machine on the network.

What happens first is that I get a macro warning about unsafe expressions. I proceed through that crap. It then opens a database in Access 2000 format (the original is 2003 format). However, none of my forms, linked tables, querries, reports etc are there. All that the database shows is 4 objects in the querries tab that are all related to the securty. The 4 objects are called:

MSysGroupList
MSysGroupMembers
MSysUserList
MSysUserMemberships

These 4 objects all contain information about the security I setup for the database but none of that actual database is there. These are the same objects taht show up when I double click on my security file.

*Update

The security doesn't seem to be working properly on other computers because I can open the database via the FE database file (without using the special link file that security adds). Don't know if that info helps.

 

[complexx]

I figured out my problems. No need to repsond to this thread anymore.