Do you warn users before starting a long process?
  v1.0 Posted at 26/04/2018 6:56 AM by Tiago Araujo

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:

  1. A table to record processes containing the following fields:
    • ALogRecord (DateCreated, FunctionName, EmpUpdated, ComputerName, ActiveForm, ActiveControl, SystemsResources, ConventionalMemory, FormsCount, TimeStart, TimeEnd, TimeTaken, RecordsProcessed, Avg, Note, RowGuide, SSWTimeStamp)
  2. 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.

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address: