Import to Uniface 10.02 - No messages for hours and still loading

Author: (Satheesh)

Hi, I'm importing the xml into Uniface 10 which was exported from Uniface 9.7 When I import the components or model or templates one by one, I get a message saying "Total number if records/rows imported : xxxx" But if I do the import of whole application in one xml, I can see the updates in log file. But at some point the updates are stopped and looks like the import process is hanging.. I killed UDE and checked the uform. The components are imported and it looks fine. So what happens during import? why there is no proper message at the end of the file? how do I know that the import was successful ? Thanks Satheesh


  1. Hi Satheesh, Every time you import a Uniface export file into Uniface 10, a check takes place right after the import to see whether migration is needed; if so, the migration utility will be started. Migration means that every records in every dictionary table that has not been migrated yet to the 'current' version of your repository, is read, converted and written back. Most changes are of a technical nature and are not reported. Some changes are reported though; from experience: assignment of unique names to area frames and labels, the removal of incorrect or irrelevant layout definitions for component variables. Those messages are logged in the message frame and the log file immediately when the migration utility encounter such a situation. Only at the very end, after the migration has been completed, a summary message is logged about the completion of the process. This message, as well as the information in the message frame and/or log file will tell you whether the process was completed successfully or with errors. For a small file (e.g. a single component) this process is short. For a large file, say several hundreds of MBs, the migration part may take quite some time and it may take a while before changes like the ones described above are reported. I can't tell from what you describe how long you waited before you assumed the import process was hanging and killed the IDE, but chances are, you killed the IDE while the migration was still in progress. (the Windows Task manager should show the IDE is still at work) When you restart the IDE after interrupting the migration process, the migration should be invoked again and continue from the point where it was when you killed it. First suggestion here is to start the IDE again and see whether the migration continues or redo the import/migration from the start. And possibly exercise a bit more patience. If that does not help, please contact us via the normal support channels, and we'll schedule a follow up asap. Regards, Henk van der Veer

    Author: Henk van der Veer (
  2. Hi Sateesh, There is a possibility that your problem may be simpler. The messages from import and migration (sometimes, depending on patch) only appear AFTER you close the Import form. Did you try to close the Import form after the log file stopped changing? Regards, Theo Neeskens

    Author: Theo Neeskens (
  3. Hi Henk, Hi Theo Thanks for the reply. Since the import was taking long time, I left running in the evening and it was in same point even next day morning. It happens when I tried again. I forcefully stopped the IDE when there was no reaction for more than 2 hours. But I'm happy that all the components has been imported which I can see in uform. So I started the IDE again. As you said, the migration started. Then at some point there is no progress. So I left as it is in the evening. But it was in the same point next day morning. I read the Migration document for 10. I found the instruction to do /all /war after import. So I stopped the migration and did that. But it is also taking long hours. But log file is updating and the components are compiled. So I leave the progress and let it happen.  I'm not sure whether this can help to complete the migration process. Thanks Satheesh

    Author: Satheesh (
  4. The compiling does not help your migration process. (After migration you do need to compile of course)

    Author: Theo Neeskens (