Reply to comment
QuickBase returns this error when you ask it to process an overly large or complex operation. There are a few ways to avoid running into this problem:
If you have one or more very large tables, you might consider archiving records you no longer need. You can easily archive using QuickBase's Import from Table feature. Please read: https://www.quickbase.com/help/import_from_table.html
If a table's not very large, it may be complex. Complex tables contain a lot of calculated fields and relationships--like an intricate formula field which includes a truckload of conditions that QuickBase must evaluate each time you display a view, for instance. If complexity is a likely culprit, examine your application setup (especially your formula, summary and lookup fields) to see if you can make it more streamlined and efficient.
If searches are returning this error, you can solve the problem by saving QuickBase the trouble of searching fields unnecessarily. Most users search an application using the Quick Find feature. (When you select "Find" from the menu and enter a term in the search box that appears, you execute a QuickFind.) This feature searches all tables and fields in an application. If your application is large or contains a lot of complex fields, this operation can take too long.
To speed searches, you can prevent Quick Find from searching certain fields (please read: https://www.quickbase.com/help/prevent_searching_in_field.html) or from searching a particular table (please read: https://www.quickbase.com/help/prevent_searching_in_tables.html). It especially helps to exclude complex fields like formula, lookup and summary fields from a Quick Find operation.
NOTE: Hiding fields from Quick Find doesn't mean that they're inaccessible. When you exclude fields and tables from Quick Find, they're still available to QuickBase's Advanced Find and can also be featured in any view. (Read about the Advanced Find feature at: https://www.quickbase.com/help/advanced_find.html)