The O7Analyzer library performs pre-conversion tasks on your Omnis7 library. During the analysis data on the composition of your library is gathered, predefined tasks are carried out and routine checks are made for potential problem areas in the conversion process. The data and a log of all the information gathered during the analysis is written to an Omnis datafile e.g. O7_YourLibraryName.df1.
The data that is gathered by the O7Analyzer is used by the O$Converter library as the source of all information about the Omnis7 library that is lost or modified during conversion. The structure of the datafile that is created when the O7Analyzer is run reflects the modules that are currently included. It may be necessary to add further datafile tables should new modules be added that require special storage for the data that they gather.
The table structure:
fBadControls | file format.......... | Used to store all bad field names that were found on window formats |
fBadFormats | file format.......... | Used to store all bad format names |
fBadProcs | file format.......... | Used to store all bad procedure names |
fCalledEventHandlers | file format.......... | Used to store names of all procedures that are called event handlers |
fInitVals | file format.......... | Used to store the initial value expressions for variables that return #??? when you interogate their $objinitval property |
fLostProperties | file format.......... | Used to store the original value of properties that are lost during the core conversion process |
fProcs | file format.......... | Used to store all OMNIS 7^3 procedure text |
fSystem | file format.......... | Used to store version Information (for Analyser / Converter compatibility checks) |
fUninitedParms | file format.......... | Used to store names of optional parameter information |
For information about communicating with modules in the O7Analyzer see The O7Analyzer API.