Thank you for your post!
When I cancel the conversion of a .fp7 file it doesn't leave a damaged .fmp12 (or any .fmp12) behind. My test files may not be as complex though. I will forward this information over to Testing and Development for further feedback.
I would also recommend posting in the Product Ideas area for:
- the conversion process should have a better interface
- it would bi nice to have more information during the conversion process, eg how much time it takes (app.)
Thank You for Your answer!
This morning, I had to convert a large V11 file to 14. It took too long, I had to leave the office and canceled while 'indexing'. The file was there, icon showed as a V14 file - but when double clicked, it wanted to convert again. It was smaller in size that the original V11 file...
I deleted that file, started over - and got a fine file (took a very long time). this time, the file was a but larger that the V11 one
I could have clicked several times on cancel, don't know how many times
This information is very helpful -if I could get just a couple other things from you:
-What is the Operating System you experienced this on?
-What version of FileMaker did you start the conversion in? (14.0.4, 15.0.1, etc.)
I am glad to hear your final .fmp12 file is in good condition!
It's on a Windows 8.1 System, FileMaker pro Advanced 14.04
The client is fully virtualized, VMWare Horizon - there is no local disk...
The source file is about 1.4 GB, FM11, brandnew - went in service this month.
We did many tests on V14 until now (yes.. we're about to migrate to 14 - we just can't deal with the pdf issue, so we'll probably stay on 14, means we have to..). It took that time as well on the testmachine - real hardware, not virtualized
Are there differencies between 14.03 and 14.04? I'm not quite sure if we have 14.04 on all clients - could be that there is a 14.03 as well.. I'm out of that office now, can't check