Leaderboard

Variations of this question has been asked countless times. Always with the same answer: Don't do it. Why would you expect a different advice this time? Move the conversion into a separate process and kill that process instead.

You can't kill it reliably and robustly. You can kill it, but expect consequences in your process.

Indeed, it is! The references are resolved in TReader.FixupReferences and are based on component names. To wire the datasource on the datamodule to the controls on the form, the datamodule has to be created before the form loads. As all forms and datamodules register themselves in the Screen.Forms and Screen.Datamodules lists, they are found by simply iterating over these lists in the Vcl.Forms.FindGlobalComponent procedure, which is registered via RegisterFindGlobalComponentProc. You can register your own FindGlobalComponentProc this way, which takes precedence over the internal one (System.Classes.FindGlobalComponents uses a reverse loop). The implementation might be a bit tricky, though.

In german language, we call this "putzig": It is indeed an error in the forums-software related to the recent change of the year. So kind of a "year 2020 bug". I do have a bugfix and will it apply this evening. Other customers reported a successful patch - so I think it will work here also.

From my blog post: But thanks for your suggestion on how to group them. I'll keep that in mind once I get to actually implement it.