The following command MicroFour.StrataFrame.Data.ConnectionManager.ShowAvailableConnectionStrings() will show the SF Application Database Connections, it would be nice and consistent to have a ViewSecurityKey property we could set before calling the ShowAvailableConnectionStrings() and let the security do its stuff.
Right now I have to add code to enforce security, and would be much better that this form acts like the MDDeployMain which you can set the ViewSecurityKey via code like this:
'-- Create the deployment formloDeploy = New MicroFour.StrataFrame.DBEngine.Deployment.MDDeployMain(lcPath & "FixTrack_DD.pkg", "FixTrack")loDeploy.ViewSecurityKey = "ImportDatabase"loDeploy.ShowDialog()loDeploy.Close()loDeploy.Dispose()
'-- Create the deployment form
loDeploy =
loDeploy.ViewSecurityKey =
loDeploy.ShowDialog()
loDeploy.Close()
loDeploy.Dispose()
On this, couldn't you wrap your own call in a security key to achieve the desired functionality? I.e. have your own security key on the menu item or button that calls ShowAvailableConnections and use that to prevent access if desired?
Hi Dustin,
Yes that is what I am doing now, but I meant for consistency through all SF features it would be easier, nicier and consistent to simply set the ViewSecurityKey.