Another change in behavior

[Fredr]

Upgrading to 3.4.2 from 3.22, I noticed antoher change in behavior. In a master\detail realtionship, doa does not refresh the detail dataset the first time the master's query is executed. Is there something I need to do differently to resolve this issue? I was able to fix the problem by refreshing the detail in the AfterOpen event of the master. I really don't want to have to do this for every relationship in the system.

Thanks,
Fred R.

 

[Marco Kalter]

I can't reproduce this problem, it seems to work just fine. Can you explain this in more detail or send me a small demo project?

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

 

[Fredr]

I was able to get around this by setting ForceMasterSynch property to true. The jest of it is that when I open a query that has detail datasets the detail datasets don't get refereshed. I have to move the record pointer in the master for the details to get refreshed. Everything else seems to be ok from there. I'll try to send you sample.

Thanks
Fred R.

 

[Fredr]

Here is a little more detail that may help. My master and detail queries are both open and both returned no rows. Now if I change the master query's sql and re-open it the detail query does not get refreshed.

I hope this helps.

Fred R.

 

[Marco Kalter]

This works fine too when I try it.

Are you calling TOracleDataSet.DisableControls? This will disable detail synchronization until it is enabled again.

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

 

[Fredr]

Yep, I disablecontrols and enable them after openning the query. I guess the problem seems to be that the details aren't resynch'd when master controls are enabled again. I think this problem was introduced on 3.3. In fact, I think we may have had the same conversation before.

Thanks for your prompt replies,

Fred R.