Hi Kevin,

>>The "no access" strategy specifies that if you don't specify anything specifically for a user that user has no access to any "secure" application objects. Have you specified "full access" for the MM user?

Yes, access is specified. The MM user doesn't belong to any group, but as an individual user MM has FULL access to all the bars when I check the access on the MM security form while the project is running. (To get to that form, though, I have to turn the 'no access' off because when it's on no users can get to anything.) Is my problem that the user needs a group? No one else here has ever tried to use security either so I have no other working projects to compare this one to.

Perhaps I have a problem because I had some security at the form level and removed it by removing it's record in the security table. (I did this because if I didn't delete the record but I removed it from the form I would get blank records in the form assigning the security to users.)

By the way, the 'no access' strategy is exactly what I need. Some of the menus will have financial reports and payroll information on them so the project must be carefully controlled. One of the big attractions for me of the Framework is that it does have the security already built in at so many levels.