ghudson
Registered User.
- Local time
- Today, 12:42
- Joined
- Jun 8, 2002
- Messages
- 6,194
Security posts - merged
Hi I've noticed totally different behavior with my secured databases in 98 and in XP.
In XP Access Security works. In 98 it is broken.
For example today I secured a database. I went to another computer running 98 and Access 2002 that was joined to the default workgroup file system.mdw . They still had full access to the database and were not even asked to enter a login. Once I joined the correct workgroup file the security was implemented though. (In XP if I go back to the Default workgroup file the security is still maintained.)
So strange. Where is the security if it is totally ignored on 98 operatings systems? Someone can just make a copy of the database and have full access in 98 despite the database being secured.
Peter.
Hi I've noticed totally different behavior with my secured databases in 98 and in XP.
In XP Access Security works. In 98 it is broken.
For example today I secured a database. I went to another computer running 98 and Access 2002 that was joined to the default workgroup file system.mdw . They still had full access to the database and were not even asked to enter a login. Once I joined the correct workgroup file the security was implemented though. (In XP if I go back to the Default workgroup file the security is still maintained.)
So strange. Where is the security if it is totally ignored on 98 operatings systems? Someone can just make a copy of the database and have full access in 98 despite the database being secured.
Peter.
Then your db is not really [correctly] secured. You should get the same result by copying the database to another computer and the user should be able to open the db without using your workgroup file. Sounds like you have joined your computer to your custom workgroup file [or worse, you have modified the default "System.mdw" file on your computer with your new security settings. Search around the forum for you problem has been asked and answered in many other threads.
ghudson is correct. The behavior you describe occurs whenever you connect to a DB using the default SYSTEM.MDW file. I have answered this question beaucoup times, so look up posts on "Security" where I have contributed comments.
To understand why this occurs, you need to know one more thing: The name of your workgroup is a registry function. You would see the same behavior when you move the .MDB to an XP machine but never join the correct workgroup on that machine. (Because, of course, the registry entry isn't changed until you JOIN the workgroup.)
Your database is not properly secured. Take a look at the Security FAQ document. Search the kb or you may find a link from here.
Why are you double posting?
At least Pat gave you the same answers as your first posting recieved...
http://www.access-programmers.co.uk/forums/showthread.php?t=107458
Hi I've noticed totally different behavior with my secured databases in 98 and in XP.
In XP Access Security works. In 98 it is broken.
For example today I secured a database. I went to another computer running 98 and Access 2002 that was joined to the default workgroup file system.mdw . They still had full access to the database and were not even asked to enter a login. Once I joined the correct workgroup file the security was implemented though. (In XP if I go back to the Default workgroup file the security is still maintained.)
So strange. Where is the security if it is totally ignored on 98 operatings systems? Someone can just make a copy of the database and have full access in 98 despite the database being secured.
Peter.
Hi I've noticed totally different behavior with my secured databases in 98 and in XP.
In XP Access Security works. In 98 it is broken.
For example today I secured a database. I went to another computer running 98 and Access 2002 that was joined to the default workgroup file system.mdw . They still had full access to the database and were not even asked to enter a login. Once I joined the correct workgroup file the security was implemented though. (In XP if I go back to the Default workgroup file the security is still maintained.)
So strange. Where is the security if it is totally ignored on 98 operatings systems? Someone can just make a copy of the database and have full access in 98 despite the database being secured.
Peter.
Then your db is not really [correctly] secured. You should get the same result by copying the database to another computer and the user should be able to open the db without using your workgroup file. Sounds like you have joined your computer to your custom workgroup file [or worse, you have modified the default "System.mdw" file on your computer with your new security settings. Search around the forum for you problem has been asked and answered in many other threads.
ghudson is correct. The behavior you describe occurs whenever you connect to a DB using the default SYSTEM.MDW file. I have answered this question beaucoup times, so look up posts on "Security" where I have contributed comments.
To understand why this occurs, you need to know one more thing: The name of your workgroup is a registry function. You would see the same behavior when you move the .MDB to an XP machine but never join the correct workgroup on that machine. (Because, of course, the registry entry isn't changed until you JOIN the workgroup.)
Your database is not properly secured. Take a look at the Security FAQ document. Search the kb or you may find a link from here.
Why are you double posting?
At least Pat gave you the same answers as your first posting recieved...
http://www.access-programmers.co.uk/forums/showthread.php?t=107458
Last edited by a moderator:
and could read it another few time to re-enforce ideas in it. It's not a big book but it methodically steps through all sorts of security issues for Microsoft Access. It was the best $25 AUS on ebay secondhand I ever spent for Microsoft Development references.
