Fun issue of the day: having a "too large" internalcalc field in a ClientDataSet nukes all field values on Post when appending a record.

-
Fun issue of the day: having a "too large" internalcalc field in a ClientDataSet nukes all field values on Post when appending a record.

I haven't found the exact limit but Size = 50000 seems OK, but if I raise it to 90000 then all other field values get nuked (zero'd) when I do Post.

No errors of course, just blank values where there shouldn't be...

Comments

  1. Stéphane WierzbickiNovember 12, 2015 at 4:57 AM

    Looks like a nasty bug. You should report it wait ha test case at qualitycentral :)

    ReplyDelete
  2. Jeroen Wiert PluimersNovember 12, 2015 at 5:13 AM

    Probably a 64k bug or so. It has similar issues that have gone unresolved for a long time. Now that
    TFDMemTable is there I'd switch to that.

    ReplyDelete
  3. Asbjørn HeidNovember 12, 2015 at 5:17 AM

    Stéphane Wierzbicki Will do once I can find time to make a test case.

    ReplyDelete
  4. Asbjørn HeidNovember 12, 2015 at 5:18 AM

    Jeroen Wiert Pluimers Sounds likely. We're working on porting the application to FireDAC, but removing BDE take precedence :)

    ReplyDelete
  5. Russell WeetchNovember 12, 2015 at 5:40 AM

    The BDE? perhaps there should be a preservation order on your app, like they do with historically interesting buildings

    ReplyDelete

Post a Comment