comment on

Well, I found the problem and almost have a solution worked out.

It appears there's some issues between the version of ActivePerl being implemented on the NFS that we use and data being pulled from the DB. When I made a separate Perl script to pull from the DB and ran it using a fresh Perl install, things worked fine.

Unfortunately, a lot of other things are dependent on the version of Perl on the NFS. Not a huge issue, just going to leave the DB work in a separate Perl script and call it from a different version of Perl.

That being said, running into a small problem with passing arguments from the initial Perl script to the now separated one. Code below:

Initial Perl:

system('/usr/bin/perl /home/SQLtoXML.pl $source_id $OutputXMLDir');
[download]

Perl script that is being called:

 my $PassedSource = $ARGV[0];
 my $FinalDir = $ARGV[1];
[download]

Unfortunately, $PassedSource and $FinalDir are both ending up as null when the program runs. Am I just passing the 2 arguments incorrectly?

Thanks again for all the help. You've been wonderful.

In reply to Re^3: Encoding issue from DBI to string by ev0lution
in thread Encoding issue from DBI to string by ev0lution

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks