Do you warn users before starting a long process?
26/04/2018 6:56 AM by
You should never start a long process (>30 seconds) without first giving a warning message to warn the user approximately how long it will take.
- Figure: Good example - Code Auditor message warning this is a long process
You will need to have 2 things:
- A table to record processes containing the following fields:
A function to change the number of seconds lapsed to words - see the "1 minute, 9 seconds" in the above messagebox - this requires a SecondsToWords() function shown. See our code base.
- ALogRecord (DateCreated, FunctionName, EmpUpdated, ComputerName, ActiveForm, ActiveControl, SystemsResources, ConventionalMemory, FormsCount, TimeStart, TimeEnd, TimeTaken, RecordsProcessed, Avg, Note, RowGuide, SSWTimeStamp)
Do you feel this rule needs an update?