Bug report guidelines

1. The basics: what you did, what you wanted, and what happened.

These are the three basic elements of a bug report. You need to tell us exactly what you did (for example, Range > Empty duplicates in selection), what you expected to have happen (to continue the example, "I expected to have all duplicates removed"), and what actually happened ("it selected the duplicate cells but didn't remove them.").
Yes, the example is silly. But if your bug report simply said "the duplicates function doesn't work," we wouldn't be able to know whether you used this function or the select " conditional select cells function, or the information " count duplicates function.

We need to be able to reproduce the problem

By telling us what you asked for, what you expected to get, and what you actually got, we don't have to guess.

2. Excel and windows version

When you report a bug please include information about the Excel and windows version you are using. To make this easier for you can go to: ASAP Utilities » ASAP Utilities Options » ASAP Utilities options and settings... Then go to the tab "Contact information" and copy the information there in your email.

3. Always search our website and documentation first

Advice so good, we'll repeat it twice. Always search within our website and documentation first. ASAP Utilities is used by a lot of users. The odds are good that if you've found a problem, someone else has found it, too. If you spend a few minutes of your time making sure that you're not filing a duplicate bug, that's a few more minutes someone can spend helping to fix that bug rather than sorting out duplicate bug reports.

4. Be brief, but don't leave any important details out.

This is a fine line to walk. But there are some general guidelines:
Remember the three basics: what you did, what you expected to happen, and what happened.
When you provide a workbook that demonstrates the problem, make sure it is small and remove information that is not subject to the problem. Otherwise it just contains a lot of information that has nothing to do with the problem, which just makes it take longer to figure out the real problem. (But don't forget to make sure that your workbook still demonstrates the bug you're reporting and doesn't have some other problem because you've accidentally removed something you thought wasn't important but was!)

5. Use meaningful, specific subject headers

A good convention for subject headers, used by many tech support organizations, is "object - deviation". The "object" part specifies what thing or group of things is having a problem, and the "deviation" part describes the deviation from expected behavior.
Bad: Little problem w/ ASAP 3.10
Good: ASAP Utilities Index sheet - Error sheet.asap not found
Bad: compile error
Good: ASAP Utilities Startup - Compile Error in hidden module: mod_menu

6. Use English or Dutch

Yes, the ASAP Utilities users are global and include a great many people who can speak a great many languages. But if you were to report a bug in a language other than English or Dutch we would probably not be able to help you.
If you're worried about your English skills making it difficult to describe the bug, you might try asking the help of a colleague or friend or provide a good example with some screenshots.

7. Don't report bugs about old versions.

Every time a new version of ASAP Utilities is released bugs are fixed. If you're not using the most recent version ASAP Utilities you should upgrade to the latest version to make sure the bug you are experiencing still exists.

You can see which version you have in the info screen. In the Excel menu go to: ASAP Utilities » Info:

8. Report a bug

If you have read the information above you can copy and paste the information from within ASAP Utilities (In the Excel menu go to ASAP Utilities » ASAP » Options » "Contact information") in your email.
You can contact us by email: bastien@asap-utilities.com.