Just to complete the story ... this was resolved soon after the email exchange.

The problem was traced to the date/time format being used on the Windows machine.

We already knew that DVBViewer used the local settings for the date divider (and hence this is configurable in DABDig) but had not realised that it used the complete local date/time syntax.

The Windows machine was set to us USA date format ... so DVBViewer required this in its API calls.

Changed DABDig to make configurable the entire date field that is sent to DVBViewer (with the default set to the standard for Europe of dd/mm/yyyy).

This worked fine and will form part of the 2.60 release.

If you need this version before it has been released then contact me.

DABDig creator