This shared property has not yet been implemented.  It is on the list, but may not make it into the 1.6.5 build since it is about to be ready to go out the door but may be in a quick maintanence release afterwards.

It informs for me if this option of between HKLM and HKCU already had been implemented in the security DLL.

---------

Portuguese for English by AltaVista Translation

Rogério Mauri

---

Agreed

Thanks, I'll go ahead and make the changes but would appreciate adding this to your enhancement list so I don't have to make the changes on each release.

Any of the forms in security could possibly be storing off the values in the HKLM registry root.  I would recommend going ahead and changing the source code on your end to use HKCU.  Long term, we'll probably change the security DLL to allow you to set some shared property to provide the path to the registry location where the form sizes/positions should be remembered.

We have a number of large customers, primarily U.S Universities, that are locking down user workstation permissions. Basically Standard User permissions and no writing to registry key HKEY_LOCAL_MACHINE.

I have changed all our registry settings to HKEY_CURRENT_USER and/or moved them to the database, which has solved the application security issues, however during testing we discovered a issue with Role Based Security Editor - When you exit editor we get a error : Unauthorized Access Exception: Access to Registry HKEY_LOCAL_MACHINE\Software\MicroFour\StrataFrameSecurity\SecurityDialog is Denied.

Is this something you will be changing or do I modify the source code on our end?

Are there other areas of the security application and/or framework I need to worry about?

Thanks,

Tim