setting security for Access 2K
We have an app we are using at work put together in A2k, (about 10 of us use it from a Share which sits on a server, 3 of us have full Access licenses and the rest are using Runtime). I want to protect the db objects from accidental changes by full license users via Access security (using the Wizard, with those charged with administering being assigned 2 sets of persmissions so they can go on as user or admin, depending on what they have to accomplish in the session).
One of my books repeatedly talks about planning for situations such as "if the .mdw gets corrupted etc.," :( Now, its sure good to have a back up plan "just in-case", but what is the likelihood of corruption? (Could this be a cryptic way of saying "the product needs more tweeking- it's not quite ready to be reliable"?)
1. Does anyone have some experience/wisdom to share on this, and 2. Am I correct that "Access security" can later be removed when (if) our IT dept decides to upsize it to SQL Server?