Nested Dataset bug

[IosifK]

The problem described at http://www.allroundautomations.com/ubb/ultimatebb.php?ubb=get_topic;f=1;t=001503#000000
about not able to update the master key using nested datasets and TMTSDatamodule still exists in ver 4+ of DOA. Can you please suggest any temporary solution for this? I tried using:

class TMTSRemoteDataModule: TMTSDataModule;
class MyRDM: TMTSRemoteDataModule;

instead of class MYRDM: TMTSDataModule

so that the pos function you use finds the required 'RemoteDatamodule' substring within the parent class name but this will result in various errors in the delphi ide because it will make the IDE see MyRDM as a form rather than a datamodule.

Any help would be appreciated!

 

[Marco Kalter]

What is your Delphi version?

 

[IosifK]

I'm using Delphi 7..
For some strange reason this doesn't happen all the time. It does happen on two or three datasets I've got on the MTSDataModule and the other 8 datasets work right. I couldn't find any differences between the datasets that successfully update the ID and those that don't. Anyway if I rename the parent class to 'TMTSRemoteDatamodule' it works for those two datasets too but the IDE acts weird on the datamodule. The company I work for has not bought the source of the DOA components so I can't find more detailed information about the problem.

 

[Marco Kalter]

Could it be that this is a master --> Detail --> Detail structure? I was looking at this, and it occurred to me that the first detail dataset (the one in the middle) might have this problem.

We'll fix this.

 

[IosifK]

No it's not that.. I've only got master-detail here. (1 master and 12 details directly linked to that master)

 

[Marco Kalter]

I will make the fix above available to you shortly. If you can let me know your e-mail address...

 

[IosifK]

iosifk@cteam.gr