It might be permissions, but I think I'd suspect your ODBC data source definitions first. Are they system-level or user level?
I get around that problem by explicitly giving DBD::ODBC the parameters for the database, rather than relying on a DSN definition. I don't recall the particulars, but thanks to [www://connectionstrings.com] they're pretty easy to find. Your connect string could boil down to something like this:
my $DB = DBI::connect("DBD:ODBC:driver={ABCD};Server=ServerIPAddress;" ."User ID=yourUserName;Password=Password");
To get the text for the ABCD slot, go into the ODBC definition thingie, and look at the list of drivers. DBI and/or DBD::ODBC may also have some methods for digging up the ODBC drivers.
When your only tool is a hammer, all problems look like your thumb.
In reply to Re: Perl, DBI, IIS question
by roboticus
in thread Perl, DBI, IIS question
by zuma53
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |