Post reply

Security

  • May 20, 2005 at 5:33 am

    #167043

    Hi

    I have an Access 2000 front end for a SQL Server database.

    Many staff members access the front end and are able to view data according to their windows network login.  This works excellently.

    However, I would like to protect the tables from being copied into another database.  I know I can protect the code with a password, or making the file an mde, but not the tables.

    Does anybody know a way of doing this without using (what I, and others, have found to be problematic)  Access security.  Also, I don't want another layer of passwords.

    Thanks

    Paul

  • May 20, 2005 at 6:58 am

    #560173

    The only way that I know of would be to remove the tables/queries from the front-end make everything SQL calls to the back-end via stored-procedures and recordsets (modules) and then lock it down as MDE.



    Good Hunting!

    AJ Ahrens


    webmaster@kritter.net

  • May 20, 2005 at 9:04 am

    #560234

    Thanks for the reply.  This is a possibility, but it can be pretty limiting for some development. 

    Surprisingly enough, I've just discovered that if you hide tables etc through the tickbox in its properties, then also hide in Tools Options - it prevents another database from seeing them to import.

    As I have lots of tables and queries.  Can anybody suggest a vb way of accomplishing this?

    Thanks

    Paul

     

  • May 20, 2005 at 9:18 am

    #560246

    Apologies, I'm talking through the top of my head.  You can actually turn View Objects back on in the importing database.

    Paul

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply