Known Issues
OMPM Reporting Tool
Size limitationsThe SQL database that all the results are imported into can handle millions of results. However, the Reporting tool becomes more and more unresponsive at databases with over 1 million records (it will timeout on a 2GB RAM 3Ghz machine). In a database with hundreds, thousands, or tens of thousands of scan results, there should be no problem at all. In databases with hundreds of thousands of records, it should still work fine but each filter would take longer to process.
If customers are concerned that the OMPM database will get too big to be manageable with the Reporting tool, here are some options:
- Have multiple smaller databases. You can create as many OMPM databases as you want
- Don’t use the Reporting tool – manually query the database (its all just SQL)
Rendering problemsIf you are using HI-DPI or do not have the Office 2007 Calibri font installed than the office reporting tool will have some misaligned text.
Office File Converter
Running ofc.exe from the command line can take an argument telling where the ofc.ini configuration file is. For example:
c:\ompm\tools>ofc.exe d:\config\ofc.ini
However, if you are specifying an INI file in the directory where ofc.exe is running from, you must append '.\' to the argument.
c:\ompm\tools>ofc.exe new.ini
BAD c:\ompm\tools>ofc.exe .\new.exe
OKOnly use positive numbers in the "TimeOut" property of the ofc.ini. Using '0' to disable the "TimeOut" feature will cause the OFC to hang.
Back to
OMPMv1