Leaderboard

10.3 and 10.4 were major versions. Then you got 10.3.n and 10.4.n as incremental upgrades. They changed this with version 11. 11.0, 11.1 and 11.2 are the same version.

In the webinar Q&A Marco Cantu was confirming that this update is binary compatible to the last version and that this was deeply tested before release. But to be honest, I would never trust such information, no matter how deeply this was tested, only because of saving a few extra clicks and re-builds of BPL's and DCU's. I usually re-build everything after every update and had no "hard-to-find", "mystical" problems and crashes ever since, at least under Windows platform.

The issue was in the following: procedure TRegExHelper.AddRawOptions(PCREOptions: Integer); begin with Self do FRegEx.SetAdditionalPCREOptions (PCREOptions); end; FRegEx is defined in System.RegularExpressions and the nearest helper was in that unit. By the way the issue is now fixed. Thanks for reporting it.

FYI CPsoftBE uploaded a fix in branch 'Limagito Patches' . Problem is solved!

You don't necessarily need threading, you just need to return control to the main UI message loop periodically. For instance, break up your loop into chunks that you can trigger with TThread.ForceQueue() for each iteration, eg: procedure TMyForm.DoProcessing(i: Integer); begin Label1.Text := 'Step ' + IntToStr(i); Inc(i); if i <= 10 then TThread.ForceQueue(nil, procedure begin DoProcessing(i); end, 200) else TThread.ForceQueue(nil, AfterProcessing); end; procedure TMyForm.StartProcessing; begin DoProcessing(1); end; procedure TMyForm.AfterProcessing; begin ... end;

As far as I understand, not the DB layer (TFields and stuff) is throwing the exception, but your Writer is, correct? If that's the case, have you seen its StringEscapeHandling-property?

Well, I guess you could decide not to cross the street in case the Wonder Of The Seas passes through

He also mentioned that there are some corner cases where it's not and he believes that we should not have those cases. Best is to recompile everything.

You should contact your DB Admin and ask him to grant you read (maybe write) access.

Please show your code. Or better create a very simple application which demonstrate the issue. Note: Il y a quelques fautes d'orthographe dans la fenêtre d'explication des étapes que vous montrez.

FWIW, the helpers embarcadero introduces in an update should disappear in the next major version, as those helpers were only used to avoid breaking dcu compatibility - so their methods will be rolled into the classes. At least that's the plan.

The one that embarcadero created will be used first, the synedit one will be ignored. Which helper is used is dependant on where they are decleared, since embarcadero declared theirs closest to the actual class declaration theirs will be seen first rather than the one on synedit.

{$IF Declared(RTLVersion111)} {$IF Declared(RTLVersion112)}