use of DBI in templates...?

[rmayer4]

I'm trying to make a template page that will take one row of information out of a ODBC database (MS Access), and use the values to create an html page to send to the user... I'd like the page sent to the user to be free of anything other than html (no javascript, etc.).

is DBI a good choice in doing this, using DBD:ODBC? or is there a better way?

Kasey Forbes
arei@selin.com

 

[goBoating]

I would use DBD::Anything, including DBD::ODBC, without hesitation.
However, I would question why you are using Access. Unless you have a
data provider that is feeding you an Access file, I would go with a flat
file setup or with MySQL or PostgreSQL (both are free).

DBD::ODBC would be a competent choice, anyway.

HTH Please use descriptive titles and check the FAQs.
And, beware the evil typo.

 

[Tve]

goBoating,

In the past I've been using the DBI.

I'm trying the Win32::OLE, and this seems to work quite well.

One main advantage seems to be the portability to ASP.

Do you have any advice?

Thierry

 

[goBoating]

If you are staying in a MicroSoft environment, then, I don't know if there would be any advantage in using the DBD/DBI stuff over OLE. The OLE approach should work fine for limited applications.

Just thinking out loud, or through the keyboard ( in this case)..... An advantage for the DBD/DBI approach would show up if you had to move your code onto another OS. You would tweak the DBD call and the connect syntax. Also, I don't know if you can use OLE to connect to a database server (SQL Server or other). If not, then it might be that the OLE approach is not scalable. If you are using it with Excell or Access and had to convert to using SQL Server or MySQL or Oracle or....., then you might run into some issues converting the code to connect to the new data source. I really have not spent much time with the OLE approach (worked some with Excell and Word files), so I can't really give a decent opinion. Maybe someone else will chime in.

HTH Please use descriptive titles and check the FAQs.
And, beware the evil typo.