Hi,
are there any further Informations about this 2 new properties?
* MasterFieldsNullable => so far, so good, will this also prevent a server call if the master field in the master dataset is null? if MasterFieldsNullable=false, there never will be a result of the detail, so the detail could be disabled/closed until the master field has a value
* SmartFetch => here i cant imagine what this will do, any help link?
ty.
MasterFieldsNullable, SmartFetch
Re: MasterFieldsNullable, SmartFetch
Hello,
1) MasterFieldsNullable allows to take into account Null values in the fields, by which the relation is built when generating the query for the Detail table. Independently on this property value, the query will be executed on the server. We can't ourselves close the DataSet (even if the field is NULL). Such behavior must be implemented manually.
2) We will add description of this option to the help shortly.
1) MasterFieldsNullable allows to take into account Null values in the fields, by which the relation is built when generating the query for the Detail table. Independently on this property value, the query will be executed on the server. We can't ourselves close the DataSet (even if the field is NULL). Such behavior must be implemented manually.
2) We will add description of this option to the help shortly.
Re: MasterFieldsNullable, SmartFetch
Thanks for your awnser
1) ok, but u could do a Truncate/ClearAllRecords in this case. Its shure that the server call will result in an empty dataset, so why call the server for this.
2) so im excited
Daniel.
1) ok, but u could do a Truncate/ClearAllRecords in this case. Its shure that the server call will result in an empty dataset, so why call the server for this.
2) so im excited
Daniel.
Re: MasterFieldsNullable, SmartFetch
1) I don't quite understand what your questions are about. Could you clarify what you mean?