Custom user security what other considerations before deployment?

[munkee]

I opted not to use the built in security management within access 2003. I have created my own authentication this typically comprises of a userID and password with a user assigned to a group.

There are 3 levels of groups all given a GroupID. In order to stop users entering certain forms and disabling certain controls on these forms I simply look up the GroupID on form_open events.

I am planning on releasing my database soon after I split it in to FE/BE and convert to MDE (access 2003). I will be using the AUTOFE Updater tool to help me manage distribution but I am wondering, what other security measures do I need to take?

I have been reading a lot about opening exclusive / opening read only / setting various forms to read/edit etc etc which I have not addressed at all in my system to be honest. There is also the fact that I have not touched the built in access security so all of the objects are owned by "Admin" without a password assigned.

Since I have created my own system do any of the above pose problems? As far as security goes I just wanted to be able to deny access to certain forms/controls which I have done. But I am now concerned with how will I ensure that users are able to add and edit data in their FE's to the BE all at the same time (or near enough). I do not want them to be able to change the design of their FEs (hence the MDE) but I do want them to all have access to the BE data, unless I have denied the forms required to do this via their GroupIDs. Any advice is welcome.

Thanks,

Chris

[hansnext]

As the user permissions are effectively at form-level in the FE I think there should be no impact on the input of data into the BE for users with the right permissions. If User Group A cannot see forms that Group B can see, they will not be able to enter data via those forms. The usual issues about record-locking will apply of course but that should not be affected by the security system. Remember to keep a master copy of both the FE and the BE before you make the MDE, as you cannot go backwards (ie., decompile the mde) having done that.