QuickBase users may notice small discrepancies when rounding
and comparing floating point numbers. For example, Round(37.785,0.01) returns 37.78 instead of 37.79. This
is not a QuickBase-specific issue; the discrepancies happen because some
floating point numbers cannot be represented exactly in the binary format
required by computers and are instead approximated.
We actively moderate comments to
the KnowledgeBase, and comments may be edited for length or content before publication.
If your comment contains one or more links to irrelevant
sites and seems designed solely to promote those links, it will be reported
to our spam filter. Likewise, if your comment contains obscene or pornographic
content, it will be reported to our spam filter.
Typically in QuickBase, forms usage is determined at either the role level, or at the report level. You can, however, use a formula URL button to call upon specific forms regardless of forms usage settings. This is useful if you‘ve created multiple data entry forms, each with their own layout, that you wish to call upon at various stages of the record entry process.
In a recent webinar a customer asked how they might use an email notification to embed an "approve" and "reject" button such that when their client opened their email, they could make the selection right there in the email and the result would be to update the record and log the client's choice to include an audit trail of the person, the decision date and time.
The table below describes some of the most common actions QuickBase performs and how they affect system performance. If you are trying to optimize performance in QuickBase, it’s helpful to understand these actions so that you can make any necessary adjustments.
If you have a QuickBase Enterprise account, you can take advantage of the Developer Sandbox feature. The Developer Sandbox provides you with a safe environment in which to try out your changes, without affecting users or data in your live application.