12-27-2011 11:43 AM
12-27-2011 12:09 PM - edited 12-27-2011 12:15 PM
Call the execute command function with the menu/commandID:
In a quick test I did, the ExecuteCommand did not fire when I raised it in the HostApplication.AfterLogon event. I did try the executeComand from a new menu I created and it worked fine.
Maybe somebody at Sage can answer why the executeCommand does not fire in the AfterLogon event.
In the past we have created our own backup dialog then called the BackupDatabase function in the framework directly like so
New Act.Framework.SupplementalFiles.SupplementalFileManager.ProgressEventHandler(AddressOf BackupProgressBarUpdate), _
Hope this helps
-- JIm Durkin
12-27-2011 01:32 PM
Thank you very much for your responses.
Jim, I thought about writing my own backup dialog but I don't want to ask the user for their name and password again.
Do you know how you can get the current logged in user and their password from the framework?
12-27-2011 02:00 PM
12-28-2011 07:03 AM
In all the examples I've seen people seem to be providing the password to the database in plain text.
Does ACT! not have it's own encryption method for password? Do we have to encrypt ourselves?