I run Omniscope on a local machine and also on a remote session on a Windows server. I have Excel installed locally but Excel is not installed on the server. If I create a data model on my local machine which points to a date in the format dd/MM/yyyy and subsequently open and refresh that model on a machine without excel then it fails as the Omniscope reader will interpret a date in the format dd/MM/yyyy as dd-MM-yyyy HH:mm:ss. I set the reader to Excel as Text (if available). Should I by default set the reader to Omniscope if I think a file may be used on a machine which doesn't have Excel installed. Are there any limitations to the Omniscope reader? Would it be possible for the Omniscope reader to work the same way as Excel? I have attached an example and screen shots. Please note I have un-ticked the auto recognise dates.
If you don't have Excel on the server then you will need to use the Omniscope reader. If you create a DataManager workflow on another machine that you intend to run on the server then you should explicitly use the Omniscope reader, otherwise you may get different results when importing the Excel data.
The main limitation of the Omniscope reader is that it has to read ALL of the data into memory. It may also be unable to read certain data types/formats and some formulas. Unfortunately it is not possible for the Omniscope reader to work in exactly the same way as Excel.