How does HotSync synchronization affect the state of my open tables?
In short: it doesn’t. When a user presses the HotSync button on a device, the operating system closes the application in the same way it closes the application when any other application is started. Consequently, the state of the open tables is recorded in the state PDB and when the user returns to the application and the tables are re-opened, the user is positioned on the expected row. If that row has been deleted as part of the synchronization, the user is positioned on the next row (or after the last row if it was the last row). What happens if I have outstanding transactions when my application ends? For applications with auto-commit turned off, an application could terminate with uncommitted transactions. UltraLite maintains these transactions so that when the application restarts, they will be there. What if a table is opened with an existing persistent name but a different index? If UltraLite finds a table in the state PDB that matches the persistent name you’ve provided, it che