Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


LO 4.o.2.2 on Windows XP Pro SP3

I am converting a 2003 Access DB that has different security settings for
different users contained in a .mdw file. I set it up in Base by connecting
to an existing ADO database and everything works fine as far as the security
settings go. 

The problem arises when I have to add or delete a new user or change an
existing user's rights. It seems that the only way I can modify the
workgroup settings is by opening the DB up in Access, changing the security
settings there and then saving the file. Then once I open the DB back up in
Base, it will honor the new security settings. If this is the only way to do
things, I can never get rid of Access! If anyone knows how I can change my
security settings in Base without having to use Access, I would really
appreciate the help.

Thanks, Dave 



--
View this message in context: 
http://nabble.documentfoundation.org/Converting-Access-2003-DB-w-Security-tp4070068.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.