Disadvantages to securing via multiple workgroup method?

[ElPresidente]

I was reading over the Microsoft Access security FAQ, but I didn't
understand why one would set permissions via code as opposed to simply
creating two workgroup files and restricting the user group. The
latter option seems much easier and straightforward. Is this just a
matter of more detailed control or am I missing something?

I'm trying to prevent users from adding/editing/deleting records from
the database itself or any linked databases. The only way for a user
to add/modify a record would be to go through a .NET front-end app I
wrote (which would connect under the admin group using the workgroup
file). Am I going about this correctly?

Thanks

 

[golfinray]

If you use a FE/BE for your database, the users have to have
read/write/edit/and delete priviledges for the BE file and the folder it
resides in. I'm assuming your on a lan. You then take the FE and load it on
each user's machine. One option would be to only load the forms and reports
on that users machine that they needed. Another option would be to go to
workgroups, but ACCESS security gets pretty hairy. I personally would not set
permissions up in code. I just load only the forms and reports that each user
needs on their computer and tie it via unc to the BE.