You will have a path/permissions problem. Debugging 101 - simplify and distill. Make a very simple program:

#!/usr/bin/perl
print "<h1>That worked!</h1>";
[download]

Exec this via a system call from your CGI using a full path call - it should work without problems. If that is the case you have just isolated the problem to you reports script. You need to understand that the user, permissions and PATH on the command line often different from the CGI case. How they differ is setup dependent. Note that -T or taint mode stops you from doing things like system(param('script_to_exec')) as you need to untaint the value before you will be allowed to use it to do dangerous things.

It seems highly likely that you are not checking for the success of open() or DBI->connect within you report script (and these are failing) but without seeing code this is just a guess.

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

This has been resolved! Changing 'system' to 'exec' and removing the taint option-T allowed me to see that the permissions of the Report dir would not allow writing by the CGI process. Thanks very much Perl Monks!