Transfering an Access Database with security file to another server

[RandV80]

Hello,

I've got a problem that has me completely stumped. At my current job I inherited a large Access database which I maintain and occasionally upgrade. I had no past experience with Access so it's been self teaching all the way. The DB is now in the process of being fully migrated into a new system (Microsoft CRM), and I need to get a full working copy of it to our 3rd party developers who do not have access to our servers.

This is what I have sitting on our server:
DB Data.mdb(1)
DB Production.mdb
DB Security.mdw(1)

There is a single Data file that contains all the Tables. There are multiple Production files, that contain the Forms, Queries, Reports, and with a splash screen front end, which all link to the single Data file. This production file is duplicated for each user, who gets a shortcut placed on their desktop (we use thin clients). Then there's the Security file, which rather than actual security is just used to join everything together. When a new user is setup they must join this security group from their account on the server.

Now I need to hand over the entire package to someone else not on the server. I initially just zipped all 3 files together and passed it on, then trying to join the security group from that end, but it didn't work. On our server any of the existing logins & passwords can be used from any account (as long as they've joined the group), but these don't work with the moved files.

I'm not sure if this is something that should be straight forward, but anything I find online focus' on setting up the initial security group, not how it works or how it can be moved. So any help would be appreciated. If more detail is required please let me know.

Thanks.

 

[odin1701]

You will probably have to make a new security mdw - I don't know much about them as that's not the way I handle security.

But as long as you yourself have access to the data (back end) and production (front end) files, then you should be fine. You just have to redesign something that will work in the new environment if making another mdw works.

 

[KeithG]

You need to create a shortcut to open the db the has the user level security. Try the tool I posted at the below link.

http://www.access-programmers.co.uk/forums/showthread.php?t=143682&highlight=uls

 

[RandV80]

You need to create a shortcut to open the db the has the user level security. Try the tool I posted at the below link.

http://www.access-programmers.co.uk/forums/showthread.php?t=143682&highlight=uls

Thanks, this could work but I'll probably need to wait till Monday to try it out. You've also pointed out an oversight of mine, while I mentioned we create shortcuts for users to access it I've always been opening it straight off the server, and this is how I was trying to open the moved version.

 

[KeithG]

ok give it a go on Monday and PM me if you have any problems with the tool. You can even add a custom image to the shortcut that you create.

 

[RandV80]

You will probably have to make a new security mdw - I don't know much about them as that's not the way I handle security.

But as long as you yourself have access to the data (back end) and production (front end) files, then you should be fine. You just have to redesign something that will work in the new environment if making another mdw works.

That's not quite it, this access DB is more of a side application for a department that can't fit into our main IS. With CRM coming in we can migrate the functionality over then completely get rid of it, the CRM developers just need a working copy to help with the design phase. I'd be happy to be on that development team but as a junior I just do application support right now