Toad 6.4 Grid count missing from Status bar

Since upgrading to Toad Datapont 6.4 the grid count keeps disappearing. If I run a script it doesn't show the grid count. Going into Tools ->Options ->Environment ->Grid and "Show Navigator Panel" is selected. If I unselect and reselect it and hit Apply the count shows up. When I run another script it disappears again and I have to go apply it again for it to show up. It doesn't appear to keep the settings even though they are selected.

I've downgraded to version 6.3 and the problem is resolved. I guess 6.4 still needs more time to work out the bugs.

Experiencing the same

@ryan.jones

Thanks for reporting this. Could you please share:

  • TDP 6.4 build version (Help > About)
  • Connection type and data source
  • Are you running the script from Query Builder or Editor?
  • Your display resolution and scaling

Thanks

It is happening to me on 6.3. It is bothersome. I have used this for years to quickly see the number of results. Now it works sometimes and sometimes not. It does not appear to matter if I am using the query builder or the editor. Sometimes it is there sometimes it is not. I have checked and unchecked boxes. I have closed and re-started, and it is still very tempormental.

6.3.0.28375

Connection type is Azure and I am using Azure Synapse

Both Query Builder and Editor do it the same.

I have 3 screens, and it does it on all of them, so I am not sure that resolution is the issue.

Also, I just did a simple select * on a table. The first one appears to always show the total. The second almist never does. Results are as follows.

1 Shown

2-5 nothing

6 Shown

7-10 nothing

11 Shown

12-15 nothing

16 shown

This pattern continues up to 36. If the number ends in a 1 or a 6, the total is shown. I stopped testing after that. The pattern seems to be the same with query builder and with the editor. It does not appear to matter if you select * or if you select one column. It appears the same no matter the number or records and the complexity of the query does not appear to matter. I obviously cannot test every single scenario, but I tested it on 5 queries. I would say that is pretty repeatable.

Thank you for sharing the information. This is a known issue, logged under the reference QAT-20314. A fix will be included in the next release, which is planned for the end of this month.

As a temporary workaround, please set your display scaling to 100%.

In the meantime, if you have any additional information or further questions, feel free to share them. Your feedback is greatly appreciated and helps us improve our products.

Thanks