in reply to DBI Long File names?

I don't see any debugging prints in there - those can really help you see what's going on. In each subroutine, just after you 'shift' the parameter(s) off of @_, print each one out just to make sure the subroutine is receiving what you think it's receiving, like:
sub get_columns ($) { my $log = shift; ### Add this ### print "get_columns sub TOP: \$log = $log\n"; my @Cols = ();
And, you should also print the sql out before each 'prepare', like:
my $sql = "SELECT * FROM $log"; ### Add this print ### print "get_columns sub just before prepare: \$sql = $sql\n"; $sth = $dbobject->prepare($sql);
You get the idea - just make sure you're getting everything you think you are. Post back your results.

Replies are listed 'Best First'.
Re: Re: DBI Long File names?
by talwyn (Monk) on Sep 29, 2003 at 21:50 UTC
    The data retrieval works fine, so long as I am accessing a 8.3 filename. It is the file access that is a problem. The minus sign seems to freak it out... haven't tried just spaces yet but I need to be able to open tables with those long/weird filenames since the application I am trying to use this as a diag tool autogenerates the tables that way. I want a tool faster than loading up foxpro to look at a log.