search

adem0x / txquery

Automatically exported from code.google.com/p/txquery
Other
0 stars 0 forks source link

TxQuery with JOINS #12

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I am upgrading an application from C Builder 2007 to C Builder XE.

I am using the latest version of TxQuery 2.x that supports XE.

I have SQL statements with multiple JOINS that have worked with TxQuery 1.86 
for YEARS and now cause EAccessError / crashes in the latest version.

The data sets attached to the TxQuery are TkbmMemTables. An example SQL 
statement that is failing is below:

SELECT EventSchedule.*,
       EventLocations.Location,
       EventResources.Name AS Resource,
       EventRevenueCodes.Description AS RevenueCode,
       EventScope.Description AS Scope,
       EventStatus.Status
FROM   EventSchedule
INNER  JOIN EventLocations
   ON  EventLocations.RecordID    = EventSchedule.LocationID
INNER  JOIN EventResources
   ON  EventResources.RecordID    = EventSchedule.ResourceID
INNER  JOIN EventStatus                                                                 
   ON  EventStatus.RecordID       = EventSchedule.StatusID
INNER  JOIN EventScope
   ON  EventScope.RecordID        = EventSchedule.ScopeID
LEFT   OUTER JOIN EventRevenueCodes
   ON  EventRevenueCodes.RecordID = EventSchedule.RevenueCodeID
ORDER BY LateDeparture,DepartTime,Resource

Has anyone else had this problem and a solution?

Best Regards,

Shane

Original issue reported on code.google.com by ShaneSt...@gmail.com on 21 Jan 2011 at 8:05

GoogleCodeExporter commented 9 years ago 
Hi, i have a similar issue do you have found the solution?

Original comment by hmesp...@yahoo.com.mx on 15 Jun 2011 at 4:11

GoogleCodeExporter commented 9 years ago 
Can you Post a sample app with sources so we can test them?
Please use latest sources I posted on Issue #15 and try to run it.

Original comment by fdue...@gmail.com on 12 Jul 2011 at 7:12

GoogleCodeExporter commented 9 years ago 
Hi Check Issue #19 for modified sources. maybe the error is fixed now.

Original comment by fdue...@gmail.com on 24 Aug 2011 at 12:59