Re: Perl, DBI, IIS question

zuma53:

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");
[download]

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.

Comment on Re: Perl, DBI, IIS question Download Code

Replies are listed 'Best First'.
Re^2: Perl, DBI, IIS question by mje (Curate) on Feb 06, 2013 at 10:24 UTC
I'm sure roboticus knows this but it might also be useful to others like zuma53. If you create a DSN and successfully connect to it you can use DBD::ODBC's odbc_out_connect_string to get a connection string you can use later without the DSN.	[reply]
Re^2: Perl, DBI, IIS question by zuma53 (Beadle) on Feb 05, 2013 at 23:01 UTC
That worked! Thanks	[reply]
Re^3: Perl, DBI, IIS question by Anonymous Monk on Feb 06, 2013 at 04:31 UTC
What worked? A system-level DSN, or bypassing DSNs entirely? Did you try both?	[reply]