Avoid RecordReference.SETTABLE-bug in 3.70

kriki

First : I don't know if this is fixed in 4.00.

rerRecordReference.SETTABLE(recMyTable);
If "rerRecordReference" has some filters or a certain index on it, these are reset with the command SETTABLE.

What to do:

rerRecordReference2 := rerRecordReference.DUPLICATE;
rerRecordReference2.SETTABLE(recMyTable);

With the DUPLICATE the record,filters and index are copied in another variable. And SETTABLE clears the filters on the new variable but leavs the first variable unchanged.

JedrzejT

Hi

This is not fixed in 4.0. When i meet this problem I don't know that is a bug. I belive this function work in that way.
I found other way to bypass that but it is very ugly

Thanks for the tip

jreynolds

I reported this bug to Microsoft and theie response was that it would be "fixed" in 4.00, service pack 1 using the time-tested method of bug fixing - changing the documentation to correctly document the behavior of the function.