Forum Discussion
QuickBaseCoachD
8 years agoQrew Captain
The issue is unlikely to be related to your table size as 16,000 records by 20 columns is that really a lot.
I do know though that when you run a report and then leave it sit for a long time, then Quick Base sort of forgets what is on that report and cannot quickly search it. How long is long, Hmmm, maybe like 5-10 minutes or so? But usually it gives a more meaningful error message to ask you to re-run the report.
But it sounds like buggy behaviour that will need Quick Base support will need to look at. I suggest that you put in a Support Case by using the HELP "?" at the top right of all pages..
I do know though that when you run a report and then leave it sit for a long time, then Quick Base sort of forgets what is on that report and cannot quickly search it. How long is long, Hmmm, maybe like 5-10 minutes or so? But usually it gives a more meaningful error message to ask you to re-run the report.
But it sounds like buggy behaviour that will need Quick Base support will need to look at. I suggest that you put in a Support Case by using the HELP "?" at the top right of all pages..
- MeghanGoddin5 years agoQrew MemberI am experiencing this problem as well. I am searching <500 records with approx. 5 columns in the report, and I can't get the search to complete.
- AudreyOppenland5 years agoQrew MemberJeff,
I had a somewhat similar issue where when I would launch some of my reports on a certain table it would churn on the clock for a long time (although it usually finally rendered back results) and others would come back almost immediately.
In the end I figured out that it was due to having unusual dates in one of my datetime fields for a couple of rows. We had loaded data via an import and had inadvertently had one row load the datetime field with a year of 1616 and one with a year of 1619. Even though these are technically valid dates in QB anytime a report happened to include 1 of these 2 rows it would take a very long time to render. Once I corrected the dates everything was fine with report retrieval.
This might not be your situation but it might be helpful to look at the data in any date fields you have and see if you have something similar.
------------------------------
Audrey O
------------------------------