Re: Win32::ODBC / IIS -- M$ SQL Server 7 on separate machine

I would strongly suggest you not use DSN's and instead form a complete connect string for the database.

the connect string would be just like one used in ASP. So if you feel more comfortable in ASP, you can get it connected there (sans DSN) and then use the connect string in Perl.

Don't give up! Perl, ODBC and SQL Server CAN play together. and it beats the hell out of ASP.

Comment on Re: Win32::ODBC / IIS -- M$ SQL Server 7 on separate machine

Replies are listed 'Best First'.
RE: Re: Win32::ODBC / IIS -- M$ SQL Server 7 on separate machine by Lexicon (Chaplain) on Oct 27, 2000 at 05:56 UTC
Well, the project deadline was today, so we actually just decided to leave it as the text database it was originally. Depending on management, I may get to come back to it later (hopefully!). I tried originally to do it with DBI::ODBC, but it failed as well. Which is why I moved over to the Win32::ODBC. I still suspect the problems to be on the database level, meaning that it will fail with ASP too. If I get the opportunity to work on it some more, I'll go sit in front of the database myself for a while and translate everything myself! ;) PsychoSpunk just installed HTML::Mason on our server, so I can get better Perl practice with a more cooperative MySQL database.	[reply]

Replies are listed 'Best First'.

RE: Re: Win32::ODBC / IIS -- M$ SQL Server 7 on separate machine
by Lexicon (Chaplain) on Oct 27, 2000 at 05:56 UTC

I tried originally to do it with DBI::ODBC, but it failed as well. Which is why I moved over to the Win32::ODBC. I still suspect the problems to be on the database level, meaning that it will fail with ASP too.

If I get the opportunity to work on it some more, I'll go sit in front of the database myself for a while and translate everything myself! ;)

PsychoSpunk just installed HTML::Mason on our server, so I can get better Perl practice with a more cooperative MySQL database.

[reply]