Issues

Discussion of open issues, suggestions and bugs regarding SDAC (SQL Server Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
ccmcbride
Posts: 101
Joined: Tue 01 May 2007 16:36

Issues

Post by ccmcbride » Wed 28 May 2008 18:45

Using :
Delphi7
sDac 4.35.1.16
when master/detail link and filtersql are equal sdac returns 0 records.

1) set master/detail relation.
2) Set filterSQL = master detail relation
dbmonitor shows :

SELECT * FROM Cust
WHERE (UID = 'CM10/22/071202384217') AND UID = :CustUID

where :custuid is the master/detail link, and mastertable.custuid = CM10/22/071202384217

running the query in studio manager correctly returns 1 record.

3) 0 records


Autorefresh on detail when master is closed is still returning an access violation.

Antaeus
Posts: 2098
Joined: Tue 14 Feb 2006 10:14

Post by Antaeus » Thu 29 May 2008 07:25

Please, try the last SDAC release (4.50.0.34). I cannot reproduce these problems with it. If the problems persist, send us a small test sample to reproduce them.

ccmcbride
Posts: 101
Joined: Tue 01 May 2007 16:36

It broke

Post by ccmcbride » Thu 29 May 2008 20:09

I downloaded and installed latest version.
I rebuilt.
I ran.
On this query:
SELECT * FROM SMPUser
WHERE (UID = 'ADMIN') AND EditTimeStamp > 0x00000000003EBECC
ORDER BY UID
I am getting this error in, shown in dbmonitor
The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions, unless TOP or FOR XML is also specified.

I have not changed any of my code or settings (other than to remove the use of daTransaction).

How to fix?

ccmcbride
Posts: 101
Joined: Tue 01 May 2007 16:36

More information

Post by ccmcbride » Thu 29 May 2008 20:55

1) dbmonitor was reporting the wrong statement with the error.
2) tracked it down to opening a query
3) the query SQL statement is :
Select RecUID, UID, PONumber, Closed, Approved From PO Where Closed = 'false' Order by PONumber (from watching the values)
4) The query doesn't seem to be making it as far as dbmonitor. The error is occurring on the qry.open statement, and being reported in dbmonitor (2.13) on a different table and connection.
5) FetchAll = false, Fetchrows = 100
6) Turning OFF QueryRecCount fixed it. I'm going to need that back.

Antaeus
Posts: 2098
Joined: Tue 14 Feb 2006 10:14

Post by Antaeus » Fri 30 May 2008 09:00

This is a known problem in the last build of SDAC. We have already fixed it.
Has the latest SDAC build solved the problem you reported in your first post?

ccmcbride
Posts: 101
Joined: Tue 01 May 2007 16:36

Post by ccmcbride » Fri 30 May 2008 16:13

I can't tell. I went dead in the water with the issue and had to uninstall it.

Post Reply