[jarendtsz]

Is there some form of restrictions on ODBC queries that were introduced recently?

We have a sales report that we run to calculate commissions that was working fine until a couple of weeks ago. We run this report for an entire month of sales.

When we try to run this report now, we consistently get an error message: Database Connector Error: ‘00000:[OpenAccess][OpenRDA ODBC]No error [Database Vendor Code: 52509]

We have since been unable to view an entire month of data for any of our sales reports. We have, however, been able to view a smaller range of data (ex: January 1 to January 15th, and January 16th to January 31st ) without a problem.

Has anyone else run into this?

Thanks

Jan
This is a cached copy. Click here to see the original post.

[ivan.parra]

RE: Limits on number of records returned in ODBC?

How man rows are you recieving and at what time did you last run the query?

[jarendtsz]

RE: Limits on number of records returned in ODBC?

Depending on the month, it can return anywhere from 5k to 20k records.

We investigated this further, and found that we can’t perform more than one function on a column without the records returned being restricted. For example:

SELECT tl.amount FROM transaction_lines tl

This will return all records without any restrictions.

SELECT tl.amount+1 FROM transaction_lines tl

This will fail, unless we do a top 2000 records. Asking for 2001 records will fail.

Likewise,

SELECT tl.transaction_id, SUM(tl.amount) FROM transaction_lines tl GROUP BY tl.transaction_id

succeeds, but

SELECT tl.transaction_id, SUM(tl.amount*1) FROM transaction_lines tl GROUP BY tl.transaction_id

fails if more than 2000 records.

This used to work without a problem until a few weeks ago. We know this for sure since we reports for the months of Nov and Dec now fail that we had run before without a problem.

Thanks

Jan

[shanondink]

RE: Limits on number of records returned in ODBC?

I used to get errors with my VB.net app if I tried to pull more than 10,000 records.

I put in a support request (#484320) on 09/28/2006 which still hasn’t been touched

Just tried again and now the error happens at 2001 records so they’ve made it worse.

If I use Excel or Access and request 50,000 records, both work fine. Why? How do we get our .net clients to work nicely.

[Author]

Posts