in reply to Re: Perl & Microsoft Access
in thread Perl & Microsoft Access

But, unless you have a specific reason for using Win32::OLE, this approach will be much less protable than using DBI and will not allow you to take advantage of the many add-on modules for DBI or the knowledge of the many monks here in the monastary who know DBI but who don't know Win32::OLE.

Replies are listed 'Best First'.
Re^3: Perl & Microsoft Access
by holli (Abbot) on Jan 13, 2005 at 19:34 UTC
    thatīs right. but if you are a windows programmer that has already used DAO/RDO-objects in other languages you might find that easier/more familiar.
    Also you can address the .mdb-files as files. You donīt have to set up an ODBC-connection for every database you wanīt to use. Acccess sees databases as files, and that is, IMHO, the most valuable feature of Access. You donīt have to struggle with tablespaces, usernames/passwords and other things that come with a DBMS like Oracle and the like.

    holli, regexed monk
      > You donīt have to set up an ODBC-connection for every database you wanīt to use.

      That's also true with DBI ... here's an example of a DSN-less connection to MS Access via DBI.

      update > if you are a windows programmer that has already used DAO/RDO-objects in other languages you might find that easier/more familiar

      good point, that's certainly one reason why someone might prefer the Win32::OLE route.