Re^3: How can I connect my perl script to an Access 2010 (.accdb) file?

will_danger:

Then I'm guessing the "Microsoft.ACE.OLEDB.12.0" bit isn't installed on your machine. I did a quick google for "ado connection string access" and found http://www.connectionstrings.com/access. Perhaps using "Microsoft.Jet.OLEDB.4.0" may work? (I don't use Access, so I'm not familiar with those connection strings.)

...roboticus

When your only tool is a hammer, all problems look like your thumb.

Comment on Re^3: How can I connect my perl script to an Access 2010 (.accdb) file?

Replies are listed 'Best First'.
Re^4: How can I connect my perl script to an Access 2010 (.accdb) file? by will_danger (Initiate) on Jun 03, 2012 at 00:33 UTC
It was a good guess, but alas, no dice. I tried the Jet connection string, with a few modifications, along with a few others. The errors I then get come from the DBI module itself, telling me that it doesn't know what drivers to use based on the connection string I am passing in. "....because I can't work out what driver to use (it doesn't seem to contain a 'dbi:driver' prefix and the DBI_DRIVER env var is not set)...". I've tried re-exporting the file as an old style .mdb file and that didn't work either. I am expanding my search a bit because this is definitely not a perl problem, but something weird with my computer or office itself. Thanks for hanging out.	[reply]

Replies are listed 'Best First'.

Re^4: How can I connect my perl script to an Access 2010 (.accdb) file?
by will_danger (Initiate) on Jun 03, 2012 at 00:33 UTC

It was a good guess, but alas, no dice. I tried the Jet connection string, with a few modifications, along with a few others. The errors I then get come from the DBI module itself, telling me that it doesn't know what drivers to use based on the connection string I am passing in. "....because I can't work out what driver to use (it doesn't seem to contain a 'dbi:driver' prefix and the DBI_DRIVER env var is not set)...".

I've tried re-exporting the file as an old style .mdb file and that didn't work either. I am expanding my search a bit because this is definitely not a perl problem, but something weird with my computer or office itself.

Thanks for hanging out.

[reply]