Using strict doesn't cause the warnings. Usings warnings does. If I comment out "use warnings;" I have no prob. The line that the warning is referring to is the middle END_OF_PRINT from the block of code that I posted. This block is encased by "&*&*&*&*&*&*&" in my scratchpad. I will comment the line itself.
Well if you did intend do comment out both the END_OF_PRINT, and the print <<END_OF_PRINT; on the second block, then the script will execute without warnings. Anytime those two here document contructs are commented out I have no issues. Otherwise, I will get the warnings.
see ya in the CB,
hok_si_la -->also listening to Cohen now.
I apologize for my previous mixup of use strict and use warnings.
As for where the warnings are coming from, they are being generated by variables within the here document starting at line 349. Any variables inside which have not been previously assigned will give you this warning and report line 349. This includes any keys in the data hash which have not been previously assigned, even if the data hash has been created.
A good way to debug it would be using Data::Dumper as previously suggested for the data hash and manually inspecting any other variables used within that here document.
First, I want to thank everyone who helped me with this via this node or the CB.
Bart/blokhead pointed out that the commented subroutine calls in my example weren't infact commented as I thought they were. This allowed me to see that the issue was with an ODBC session I was having within the subroutine (printOwners) itself. I instead decided to use DBI and everything seems to be working great.