Recent content by giga

It is strange that in a few cases the support stopped answering... I think that answer like "you do not have a service contract, we will not fix the bug" is better than silence...

Based on table type and some setting the row can be moved during update (due to better performance) and at that case the rowid is changed. And modified by another user is reported....

Dear Marco, is there a chance that this bug will be fixed soon? Thanks and kind regards

Dear all, how can I monitor the 64bit application? The sql monitor shows nothing when application is compiled as 64bit.

Dear Marco, any news? Any comments? We really appreciate your comment and fix.

Dear Marco, it is really so hard to implement this bugfix?

How can I monitor the queries made by 64 bit application. The monitor works only for 32 bit applications. I have problem with the performance: When I run 32 bit app the query for a report takes 1 second. When I compile the code as 64 bit it takes 20 seconds and the mouse pointer changing many...

I did some research and there is result: - when the field is created it has DataType ftString - when the QBEMode is set to true, DataType change to 231 That's why the SQL is not correctly generated because you do not count on DataType 231.

Please can you let us know what we can do? What is your plans with that. This bug has been reported since 19-07-2013. Thanks and regards

Hi Marco, thank you. As I told before - varchar2(10), defined as TStringField at TOracleDataSet. To reproduce: create table test (x varchar2(10)) sql.text := 'select x, count(*) from test group by x'; qbemode := True; qbedefinitions.field[0].Value := '01234' ExecuteQBE

This problem still exists at DOA 4.1.3.5 on XE6. It makes the DOA unusable for us! When it will be corrected? Is there any workaround? We can not use 'ResolveToDataset := True'

I have a simple select that do grouping where X is varchar (string) field: select x, count(*) from table group by x; When I do QBE on the field X, it generates having clause without quotas and select crash!!! select x, count(*) from table group by x; having (x = 01002) /* Modified for QBE */...

Sorry this is not true for a case when stored procedures are used for the update / edit. In this case the OracleDataSet doesn't have to have these information. The bug is probably somewhere in PSGetKeyFields (as shown above) Thank you! Your product is great! (except these small bugs)

I have ODS connected to ClientDataSet via provider. The SQL contains stored procedure and insert/update/delete is maintained via provider BeforeUpdareRecord with stored procedures. Unfortunatelly I have to load fields into ODS or set ODS.UniqueFields property. Without this it crash with Access...

Hi Marco, I have similar problem. I have ODS connected to ClientDataSet via provider. The SQL contains stored procedure and insert/update/delete is maintained via provider BeforeUpdareRecord with stored procedures. Unfortunatelly I have to load fields into ODS or set ODS.UniqueFields property...