Leaderboard

Delphi has always been inexplicably poor for calling external command line programs; FreePascal is actually much better at it (as is most everything else). This is the standard code every Delphi user seems to use to do what you want (because only @Remy Lebeau and @David Heffernan understand it): https://stackoverflow.com/questions/9119999/getting-output-from-a-shell-dos-app-into-a-delphi-app

TECNativeMap is a 100% Delphi mapping component using neither browser nor javascript. It is available in VCL and FMX for all platforms. Main new features of the last version Layer for OverPassApi (OpenStreetMap data import) TomTom routing engine, and layer for road incidents Support for IsoChrones Wizard to draw paths (road, bike and foot) in a few clicks You can download a trial version for Delphi 11

Sure it could. I wouldn't. Field values are better and much more flexible. In general, if talking about your client-side replication (which I rather call duplication), I consider the following scheme to be more or less correct: - Start transaction on Master blocking access to record (if DB engine can do this) or to table - Start the same transaction on Replica - Update Master - Update Replica - Commit Master - Commit Replica - In case of any error rollback both - In case of error at Replica only - you seem to have troubles. However, this scheme will only work if both DBs are online. If any of them goes offline even for a second, the state could get unsync'ed. That's why replications usually made at server side. Either with update logs filled by triggers (but be careful with rollback'ed transactions!) or some kind of "last modified" marks. Anyway Nexus doesn't seem the good choice for this. There are plenty of opensource DB's which have replication out-of-the-box