MS Access Dependencies

[nealparr]

I'm hoping someone can help me. I'm using an Access database with my SWFKit Pro 2.2 application and everything is working great. My question is what .dll's ect? Should I include in the attachments to ensure that the Jet 4.0 drivers are installed on every end user's computer?

This is the provider I'm using:

Microsoft.Jet.OLEDB.4.0

I read the database tutorial on using Firebird. What .dll's are required for Access?

Thanks in advance.

[Snapz]

Does this help ?

The runtime library has only one file, the 'fbembed.dll', which can be downloaded from the FireBird official site, or get from the deployment package. We must rename it to 'gds32.dll' for the FireBird ODBC Driver requires it to be 'gds32.dll'. The odbc driver contains three dlls, to install it, just register the 'OdbcJdbcSetup.dll', which is one of the three dlls.

[nealparr]

Thank you for your reply. Unfortunately, that's for the Firebird database drivers. I'm wondering what dependencies are needed for the MS Access database drivers.

[SWFKit]

You don't need the firebird driver, but need the Jet OLEDB provider, which can be downloaded from http://msdn.microsoft.com/en-us/data/aa937730.aspx. In swfkit, you connect to databases with the Microsoft ADO components. For every type of database, a specific oledb driver is needed. For example, Access needs Jet, Mysql needs myodbc, etc.

[nealparr]

I know that. I am wondering what .dll files to package with the program in case the end user doesn't have MS Access. I need the Jet filenames that are required for distribution. Like in the Firebird tutorial it listed what .dlls were needed. I need the list for Access.

[nealparr]

Do I just need the odbcjt32.dll file, or do I need more than that packaged with it?

[SWFKit]

No, you cannot just pack the dlls. You will have to run the setup file of the jet engine provided by Microsoft.

[nealparr]

Thanks for the reply. Apparently, the drivers are installed by default since Windows XP SP2, so it's probably not even necessary unless one is targetting older computers. I think what I'll do is detect whether they are there before running a db connections, and then prompt the install if they're not. Appreciate the help, thanks.