>I understand what you're saying, but our end users LOVE how easy it is to configure security in their MM VFP applications via the user interface. If they have rights, they can go into security setup mode, right-click a control and set permissions on the spot. This is much easier than sending them to a separate user/role form where they set security.
>

Hmmm... perhaps I am saying something wrong. Perhaps I don't understand what you are saying.

In the MM.Net security, lets say you have a role called "Clerk", and "Clerk" has NOACCESS to the ee_master.salary field. Is that inforced in the bizobj, so if I instantiate the bizobj and call GetDataSet the salary field is null? Or, is it the UI control that just stays invisible?

I guess the later of above would be OK, as long as my Windows, Web and Mobile UI's don't need any extra work to specify that the salary control is invisible and all use the same security data.

Does that make sense?

Thanks Kevin... the interface to setup security in VFP MM sounds cool. I have never seen it.

BTW: I am curious if you have a time line for a final release? Or, at least for a beta with the security system built in? Also is the license an annual subscription or would you just have to pay for new versions as they come?

Thanks,

BOb