Giving an executable permission is not enough. An executable script needs a line at the top which indicates the interpreter to use. For Perl, this is like
#!/usr/bin/perl
For php, very likely it's
#!/usr/bin/php
if you would like to invoke the php script without calling php directly. This seems to work on my system with a simple test.
By the way, I think it would have been more coherent if you continue with your previous thread rather than starting a new one.
If you explicitly invoke perl or (or just any interpreter) to execute a script, as in "perl script.pl", script.pl needs not be given executable permission to run at all.
If you would like to directly invoke the script, e.g. "./script.pl", the file needs the top #! line in order to tell which interpreter to use to execute it, and the file needs to have executable permission set.
Then the script you are referring to seems to be not that well written. A really good script should not really care from which directory it is invoked and still does its job properly.
If the script can't be fixed to function that way, or it's supposed to be only invoked this way, the only way left is to invoke instead by
cd /home/users/ElburdNDL/www/cgi-bin && perl script.pl
If this works on the command line, just paste this onto your cron line.