If you clicked on a column header, then that column header needs to be suppressed from sorting.
If you did something that normally takes a second or 2, then it could be that you have a corrupt database. If that is the case, test the setup (globalmaster.fdb and live.fdb) on a different PC where no hanging issues are experienced. If that PC hangs in the same place with the data from the faulty db, then you have a corrupt database. On the server:
In Veculim, open File Manager, Tag All and select DataSet Tables from the drop down option and Export to XML. This will export all the data to the C:\ProgramData\Veculim\SharedData\\Export
Close Veculim (on the server and all workstations).
Rename the existing database file (probably live.fdb) to liveOld.fdb and move to an old folder.
Copy the BlankDatabase.fdb to live.fdb
Run Veculim with the following 3 command line parameters: /RuntimeFileManager /NoFieldValidation /NoImportData. This will bring up the Runtime FileManager window. Click Tag All and select DataSet Tables from the drop down option. Then click Import and select the C:\ProgramData\Veculim\SharedData\\Export folder.
Once that is complete, move the xml files out of C:\ProgramData\Veculim\SharedData\\Export to C:\ProgramData\Veculim\SharedData\\Export\old
Run the export again.
Compare the xml files in the C:\ProgramData\Veculim\SharedData\\Export\old to the C:\ProgramData\Veculim\SharedData\\Export files.
Veculim hangs at a point in the application