ClientDataSets and DOA

[shannonwrege]

I just recently upgraded from version 3.3 to 3.4 of DOA, and all of my ClientDataSets no longer work properly. I think this is because of the enhancement in 3.4 that copies Params values into the variables ...

Delphi/C++Builder 5 Provider Support improvements

• Params from TClientDataSet are now copied to TOracleDataSet
  
• Fixed 'UpdatingTable required' error message for cursor datasets

I have always been accustomed to defining the variables in the OracleDataSet, setting the variable values using SetVariables, and then opening the ClientDataSet. My ClientDataSet had no params. Now my problem is that the variables get cleared out when I open the ClientDataSet. I have this kind of code everywhere.

Is there a way to disable the copy?

Can the product be enhanced for backwards compatability (e.g. if the Params are empty, do not clear out the Variables)?

Thanks for any help.

Shannon

 

[Marco Kalter]

The fix allows you to control the variables in the server application through the Params of the ClientDataSet. This includes the situation where no variables are present.

All you need to do is right-click on your TClientDataSet and select the "Fetch params" item from the popup menu. At run-time you can call TClientDataSet.FetchParams.

------------------
Marco Kalter
Allround Automations