Stephen Huston

FileMaker 12 Conversion.Log: observations

Discussion created by Stephen Huston on Apr 6, 2012
Latest reply on Apr 6, 2012 by Stephen Huston

Just passing along some info from my analysis of a big conversion to FMP12:

 

28 files converted as a batch, one entire server directory of FP7 files, total of 11 GIGs due to one graphics storage file. This was a backup set from our live server.

 

Conversion took 30 minutes on a 2-yr old iMac 10.6.8

 

The Conversion.Log file was 4960 lines long. I renamed the log as a .tab file and imported it into FileMaker 12 to test individual line values.

 

All lines showed Error = 0 (yea!)

 

Indexing was rebuilt for all indexed fields, 1781 instances in these 28 files.

 

Reindexing messages reported differences between original and final index values on 17 lines, but just different fields. Some of those 10 fields showed changes in both the value index and word index for the same field. Only 3 of the 28 files had changed indices after conversion, but one of the appears to have completely rebuilt a faulty index because the difference reported on one field was 9765 value index changes, and 9704 word index changes.

  • That file/field will get looked at closely before we do the final conversion on the working copies sometime down the road.

 

The message on 183 lines was "Recovering field..." which was followed by reindexing on that field. Don't yet know what caused recovering of field or exactly what it implies about the prior state of the field. This happened to one or more fields, but not all fields, in 24 of the 28 files.

  • Would love to know what that indicates.

 

The graphics storage file was the same size immediately after conversion as before: 9.82 GB exactly.

 

The File Format line for 25 of the 28 files was: Product version: '8.0', File Format version: '7'

  • Those 25 files had been converted from FM6 directly to FM8 (not 7 apparently, before my time on this project)

2 files built with FMPA 10 showed: Product version: '10.0', File Format version: '7'

and the real surprise was the one file added from scratch in FM11, which read: Product version: '11.0', File Format version: '11'

 

That's it for the moment.

 

Stephen Huston

Outcomes