order by with clientdataset

[rcoyle]

I am using DOA version 3.4.6.4 with Delphi 6 and Oracle 9I. I am developing a 3 tier application. I have set up a toracledataset that contains an order by clause. I tested the query using the Toracledataset and the proper number of rows are returned. When I open the same query via the clientdataset in the client application only 3 rows appear. The three rows will appear if I open and close the dataset at runtime or designtime. If I remove the order by portion of the select statement all rows are returned in the client. If in add an index to the client all rows appear. Does anyone have any idea as to what is causing this problem and the best solution to resolve this problem? [Eek!]

 

[Marco Kalter]

Did you enable the opNoDefaultOrder option of the TOracleDataSet.ProviderOptions property?

 

[rcoyle]

Is this a property of the TOracleDataset or the TDataset provider? It appears in neither in my version of these components.

 

[Marco Kalter]

It's a TOracleDataSet property, with four options:

Declaration

type TOracleProviderOption = (opNoKeyFields, opNoIndexDefs, opNoDefaultOrder, opNoCommit);

type TOracleProviderOptions = set of TOracleProviderOption;

property ProviderOptions: TOracleProviderOptions;

Description

The ProviderOptions property controls the behavior of a TOracleDataSet when connected to a TDataSetProvider:

opNoKeyFields      The dataset will not attempt to determine the key fields.
opNoIndexDefs      The dataset will not attempt to determine the index definitions.
opNoDefaultOrder   The dataset will not determine the order by clause of the SQL statement.
opNoCommit         The dataset will not commit transactions. You will have to implement your own transaction management in the server application.

 

[rcoyle]

Ok, but in my version this property does not appear in the object inspector. This must have appeared in version >= 4.0. Does this mean that you no longer need to use a Borland TDataSetProvider?