VisualCron

VisualCron does accommodate continuous file processing. Like packing and unpacking compressed files, splitting or merging files, sending E-mail's and executing queries on databases. VisualCron in less suitable for performing very complex operations on files like, arithmetic with numbers, dates or amounts. Very complex job scripts become cluttered. Debugging Job scripts is not easy.

Incentivized

• VisualCron can pack and unpack files from many types of packing methods.
• Clear job scripts with complex constructions can be written in VisualCron
• VisualCron provides a clear graphical overview of the situation of all jobs.
• VisualCron clearly indicates when a job has run into an error.

Incentivized

• VisualCron should more specifically indicate the root cause of an error.
• If copying a file goes wrong, VisualCron reports 'can't copy file'. I expect 'no read permissions from original' or 'no write permissions from destination'.
• VisualCron offers no way to execute a Job script line by line
• In VisualCron, nested loops cannot be created.

Incentivized

Questions and problems can be addressed to VisualCron 's support department via E-mail. I usually get a good answer from them fairly quickly. There is also a VisualCron forum where you can ask questions that will be answered by other VisualCron users.

Incentivized

For simple processes, VisualCron is easier to use and maintain. For complicated processes, Quadient Inspire offers more options. The graphical representations of waiting, running or completed jobs is adequate for both products. The logging of job actions is better in Quadient Inpire as in VisualCron.

Incentivized

• With VisualCron, I need 3 times less time to get file processing right.
• If a VisualCron job goes wrong I need twice as much time to find the problem.
• Visualcron does not run on Linux but on Windows which can make an upgrade and reboot take up to 6 times as long.

Incentivized