forum.e-valid.com

Afternoon.

What is the unifying principle for eValid's support files?

Such as: log files, timing files, and all the rest?

Thanks

FrankA wrote:Afternoon.

What is the unifying principle for eValid's support files?

Such as: log files, timing files, and all the rest?

Thanks

Fair question: why did we do what we did and not some other thing.

In building a tool a prime directive (in our opinion) is that it must be simple.

We believed -- and still do -- that a good product has to be able to interface with a wide range of other products.

So, for eValid the rule is, blank delimited and strings with no instantiated blanks.

Here is the documentation page that addresses this:

http://www.e-valid.com/Products/Documen ... rmats.html

We could have left it that way, but we did includ one type of file conversion built it.

Most of the log files convert quickly to XLSs.

The only exception -- when you can do your own formatting in an output file -- is when the script creates a file with the DOM input/output operations commands, described here:

http://www.e-valid.com/Products/Documen ... utput.html

In this case you are using standard "C" language formatting rules.

Hope this answers the question/issue.

-- eValid Support