Port Sight Secure Access Locking Accounts

For those of you using Port Sight's Secure Access version 2.2 or prior- here's a little bug that I've notified them about and requested a fix.
During the insert of the new user, object or relation through the use of Proc_AR_User_Insert, Proc_AR_Rleationship_Insert, or Proc_AR_Object_Insert the ObjectValidFrom parameter is accepting the date from the client machine. This causes a problem when authenticating because the objetValidFrom datetime value is being compared to DateTime() on SQL Server. If the client and server times are not in sync authenticating immediately after inserting a new user will result in Account being Locked out.
I've sent in the request to Port Sight to have this fix but in the meanwhile a word around would be to add a line of code to the stored procedures which overrides the objectValidFrom date with GetDate() from SQL. Since the comparison is being perform against GetDate() then GetDate() should be used for inserting the timestamp into the record.
This took about 3 months to find - we've dealing with this problem for months and we finally set some time aside to disect the problem and find a fix.

Long process got you stuck???

You ever click an OK Button do execute a long process and you can't do anything on the form??? Literally has you stuck! It doesn't refresh, it doesn't let you hover your mouse into the form, it just doesn't let you do anything!

Here's something for you to try: Application.DoEvents();

Allows long running process to execute misc. events on the form.