FredS

This annoyance did happen but seem fine in the release.

The Artificial Indexers are good at returning other peoples work, when asked a second time they return more work of yet another person in a completely different style and syntax.

Somewhere in all that info in those two links you can see that AutCommit "may" mean CommitRetaining.. Either way, do a Trace and you will know why this happens.. far easier than attempting to find the cause in code.

To be sure add a TRACE to your db (server end), actually pretty simple thing to do. Check this out: https://stackoverflow.com/questions/77201632/growing-firebird-database-caused-by-commitretaining/77202004 More: https://docwiki.embarcadero.com/InterBase/2020/en/Using_isc_commit_retaining() You have to call Commit to end a chain of CommitRetaining. If your TConnection uses Rollback as its default action all is lost, change that to RollbackRetaining. But without Commit and while using Pooling this can get messy because the default query is usually set to ignore non committed data.

I once sent out an app after a Delphi update and the new GetAce declaration broke it.. they left it that way for years.. The funny part is that others have run into GetAce issues and where told to switch to WinMD 🙂 RSP-44096 was my second attempt to try a newer version of WinMD. Other issues from the prior one have died in the old system. Anyhow, if you claim to build the API using the M$ supplied db and I can't trust just one single function then I have to assume there are more hidden issues..

May explain an old bug report I file where adding a second record helper (access to private as a bug fix) lower down in a unit would be ignored. There may be a workaround for class helpers, in this case you can inherit from the original class helper. THelper2 = class helper(THelper1) for TMyClass

Tested it on W10 in Common folders like "Program Files" and it worked well.

To test this out I used an app which requires elevation. The error below seems like an awkward way to handle this.. This Errors with "The requested operation requires elevation" when executed from a non elevated process. More info here: https://stackoverflow.com/questions/4713196/createprocesswithlogon-error-requires-elevation

..and if your hotel runs an internal network?

The User token must exist else you cannot enable it. Also Impersonations work on a thread basis, it may not be possible to use the Main Thread for this! It may be worth your while to supply us with Process Explorer details as Kas has.

Managed records took a long time to fully implement and yes, records with strings where not managed or let's call them pseudo-managed and allowed. That only leaves the Q why fix or enforce this in: 12.2>12.3..

What I found when originally searching: https://stackoverflow.com/a/64526312

Seemed fine on a smaller section of code base but the same code base in the new 64-bit preview was a disaster..

Same, I've had to recompile several design time packages to solve this.

This dates back a while, pretty sure some cross certificate (driver signing) issuer supplied this as part of an example on how to sign.a driver. I only recall because I had to remove it when we stopped cross signing everything.