DBI is not especially fussy about which database you use behind the scenes.
I'd just try using one of the ODBC interfaces, preferably the DBI version DBD::ODBC (rather than Win32::ODBC) or I notice that there is a DBD::ADO available. Also, DBIx::SQLEngine may be of some use. Not used any of these, so this is not a recommendation, just some pointers to more info.
Hope that this helps.
Cheers, -- Dave :-)
$q=[split+qr,,,q,~swmi,.$,],+s.$.Em~w^,,.,s,.,$&&$$q[pos],eg,print
| [reply] |
I think you really should give DBI a try, because it's the de facto standard database interface for perl, so it's probably better supported. Also, it will be easier to switch to other databases and you can reuse more code. It's not all that different from ODBC, so it shouldn't take you too long to learn.
I'm not 100% sure that Class::DBI supports DBD::ODBC (the DBD::XXX modules are the database sepecific drivers for DBI) but in theory most of it should work. Give it a try. If it doesn't work, ask the Class::DBI mailinglist. they're a helpful bunch of people.
Cheers,
Joost.
| [reply] |
In addition to DBD::ODBC, you can also use DBD::Sybase to connect to SQL*Server. It so happens that Microsoft chose to build SQL*Server from Sybase 4.3. :-)
------
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
I shouldn't have to say this, but any code, unless otherwise stated, is untested
| [reply] |