I have a network database with an archive table of records that are transferred and no longer in use. Aside from the Administrator, I only want those in the "Screening" group to be able to append records from the Active table to the Archive table.
The process involves two tables (Active and Archive) and two queries (Archive Append and Archive Delete), with the queries running through a macro (which first appends marked records to the Archive table, and then deletes the marked records from the active table). Records are tagged as "Transferred" (a check box), and the macro takes care of the rest.
Here's the issue. The Administrator can run this macro with no problems at all, but those in the Screening group cannot if they are not running from my computer terminal. I created a test account that only has Screening group permission, and it runs fine from my terminal, but anyone else gets an error that they do not have permission to append.
Could this have to do with my security.mdw file? All other desktops run the database through a shortcut that points to the security.mdw file (so as not to cause problems with other Access programs). The only workaround I've found is to give Administrator access to the few people in the Screening group, as I've tried giving full access to the applicable tables, queries, and macros -- but no change.
The process involves two tables (Active and Archive) and two queries (Archive Append and Archive Delete), with the queries running through a macro (which first appends marked records to the Archive table, and then deletes the marked records from the active table). Records are tagged as "Transferred" (a check box), and the macro takes care of the rest.
Here's the issue. The Administrator can run this macro with no problems at all, but those in the Screening group cannot if they are not running from my computer terminal. I created a test account that only has Screening group permission, and it runs fine from my terminal, but anyone else gets an error that they do not have permission to append.
Could this have to do with my security.mdw file? All other desktops run the database through a shortcut that points to the security.mdw file (so as not to cause problems with other Access programs). The only workaround I've found is to give Administrator access to the few people in the Screening group, as I've tried giving full access to the applicable tables, queries, and macros -- but no change.
