[RESOLVED] Distribution/Setup almost works

[gwboolean]

I have put together a distribution package, using the Setup Wizard project. The package includes the database used, an Access X64 database.
I assume that I set the package correctly, although I have and can add whatever might be helpful from the distribution project.

I put the distribution setup files on a SD drive and ran the setup on an older computer that I am no longer using. The setup ran fine and loaded.

I started the application and on the open screen I got a message stating that

The OLE DB 12.0 provider is not registered on the local machine.

The application opens, but there seems to be no database to work with.

I am not sure what this is telling me. My interpretation is that this machine, for some reason, will not run the database. Is there something I need to set somewhere on the machine I am loading, or is there something that I need to do with the database prior to distribution? Or is this message telling me something completely different?

[jdc2000]

Possibly useful link:

https://stackoverflow.com/questions/...-local-machine

[gwboolean]

Thanks,

From that I get the idea that my connection string might be the culprit. Anyway, I am going through that and seeing what I can do with it. My current connection string is below.

I have the X64 version of ACCESS and have set everything that I know to set for X64 instead of any CPU, or x32. It is likely that the verions on the system that I tried to load it on is probably x32. Could that be the issue?

Public MasterBaseConnection As New OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\SiTech\Development\SiTechSolution\PlanMaster (P)\PlanMaster.accdb")

[jdc2000]

Is Microsoft Access installed on the old test system that you are installing your application on?

If not, did you install the AccessDatabaseEngine on that system?

[gwboolean]

I think that the machine has the x32 database engine installed. I had thought of that as a possibility, but then I thought that whatever was setup on the target machine was irrelevant. I will check and make sure that the target machine is setup with the x64 database engine and see if that resolves the issue.

Thanks,

[gwboolean]

I had to uninstall the x32 database engine and install the x64 database engine on the target machine. It's all good now.

I had thought about that before, but I just didn't believe that it should apply to a target machine. I had thought that everything that was needed was in the distribution package.

Thanks for overcoming my reluctance to do the right thing!