More than one MDW file

[PaulJK]

I have a secured database and I need to have an identical separate database. The difference is that one database is for one county and the other is for another. I have been asked to have two separate databases rather than combine under one.

There is no problem buliding the second database as it is clearly a copy of the first. However I would appreciate some guidance on how to work with the MDW file.

The current database is secured and has an MDW file. Is it OK to use both MDW files across both databases. Should I have another MDW file and through the use of a shortcut to open the new database use the other MDW file.

Your advises would be appreciated.

 

[gemma-the-husky]

you may not need any mdw files at all. (other than system which is implied)

basically an unsecured dbs is secured against the system mdw. this logseveryone in as admin, and therefore gives everyone full rights. you can hide the dbs window, and if you trust your users and dont need to protect your design, there is no reason to go further.

by having an mdw you can assign different rights to each user (more normally to a group of users), and thereby prevent certain users seeing different forms.

if you therefore want say, inputters, admin users and power users, to have different facilities, you can then determine that particular forms can eg be read only or given full use by a particular group.

if you have multiple mdws it makes life hard for users as they will have to keep changing the mdw they are attached to for the moment (you can of course put desktop icons that open the particular app with the correct mdw ) Generally in a single company, you would only want to have a single mdw, but you need to plan this carefully. Be careful because if you "lose" your mdw you will struggle to recreate it. it is not just the name of the mdw that is significant.

Alternatively, and i am sure there are lots of examples on this site, you can design your own front end to log users in.

Hope this helps