-
Result Set Display Error
We use ASP-DB gold on Windows 2003 and NT Servers, querying against a Teradata DB. When running an aggregate query, the displayed table only returns the number or rows that equal the value of the aggregate in the first row of the result set.
For example if results set is:
Staff AggregateValue
Bob 5
Mary 19
Gus 62
The table will display 5 rows and the footer summary will show 1-5 of 5. If we eliminate Bob in the SQL query, the table will diplay 19 rows and the footer 1-19 of 19. If we drop Mary and Bob from the query, the table will display 1-44 of 44 because Gus's aggregate total is greater than the total number of rows returned (44).
Why is ASP-DB using the first row aggregate value in the result set as the row count of the result set?
-
Let's make sure we are looking at the right angle...
1. In order to truely debug this or any 'strange' problem. Either the DB can be accessed or user make an equivalent NWIND or MS-SQL sample. The sample can then we loaded onto a public server so both side can see the debug. For now we can only do a 'blind' debug.
2. Row Count of result set is obtained from -
a. No dbCountSQL specified - SQL build by system like ACCESS, SQL using 'TOP', MySQL using LIMIT.
b. dbCountSQ specified - System wil use it like SELECT Count(1) From Table.
c. dbCountSQL = "none". System will use dbSQL to count. The slowest but always work.
So I suggest you to set dbCountSQL = "none" and see whether the Count is correct. If no, then it is really strange!
Fk
-
I found dbCountSQL yesterday in the manual and it looks like a possible answer. You refer to dbCountSQL = "none", the manual refers to dbCountSQL="lowspeed".
Is there any difference? Which is the correct syntax? Is there any way to see the value of dbSQLCount during the query run?
Thanks
-
OH.. my fault... none is for tornado. lowspeed is correct...
BTW.. please consider going to Tornado... it is an even exchange for you if your maint. is uptodate .. no need to pay more. It is more efficient and overall better.
Frank
