Alexander - Omniscope Source blocks for data files feature 3 different Excel import drivers, and Source blocks for database imports offer two different Access import drivers, each with their advantages and disadvantages. Equivalent data flows may be defaulting to different drivers when you upload the file to the Server that has no copy of MS Office.

Check which import driver is being used in each case by opening the relevant Source import blocks. Post back and we can determine the best course of action.

Hi Alexander, what is the difference in the behaviour? Do you mean that the data is different? As Tom mentioned Omniscope uses different methods for reading data depending on whether you have Omniscope installed. We expect there to be slight differences, however we would be happy to investigate this further if you can provide us your IOK and source files.

Hi Thomas and Chris,

Just to make sure you understand me correctly. It is one file that I open on my laptop and the server. The inputblock is "Batch append files". I cannot find any settings for import drivers.

No problem to send you the file, but is it an idea I show you the problem in a screensharing session? You might be able to solve the problem on the fly.

Ok thats fine, i'm in the office for the next hour so feel free to call me here.

Hi,

After a discussion with Alexander the problem lies with using different readers to import the Excel data. On the machine with Excel installed Omniscope is using the "Excel as text reader". On the machine where Excel is not installed Omniscope defaults to using the "Omniscope" reader. Because of the structure of the underlying Excel worksheet this produces different data. We recommend that if you are creating a DataManager workflow that is likely to be run on a machine where Excel is NOT installed, you should always use the "Omniscope" reader.