How to deploy a VB.NET solution with access database

Question

0.00/5 (No votes)

See more:

I have an Access 2007-2010 password protected database with a VB.NET front end. The Access database is located on a shared network drive for a small group of people to share. The PC's I am installing the VB.NET front end on may or may not have MS office with Access 2010 or 2013 installed.

When deploying the solution, I have also been installing the Access 2007 run time which seems to work fine. This does not seem to interfere with installed Access 2010 or 2013, but does require administrator privileges.

Is there any way to get around installing the Access 2007 run time?

What I have tried:

Connection string used is as follows:

<pre>OLEDBConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=" & DatabaseLocation & ";Jet OLEDB:Database Password=" & Password & ";"

Posted 5-Aug-18 14:33pm

Bobbo56

Updated 5-Aug-18 14:34pm

v3

Add a Solution

Comments

CHill60 6-Aug-18 7:36am

Why get around it if it works? And why not use 2010 runtime anyway?
Many, many installs these days require administrator privileges (at least on corporate installs) - is that your only problem?

Bobbo56 6-Aug-18 9:20am

Yep, sort of a minor problem. Only wondering if there were a more efficient way of doing it. Not using the 2010 version because there are 32 and 64 bit versions (if I remember right) and you cannot install a 32 bit version if Office 64 bit has been installed. Struggled with compatibility years ago with the first version I wrote and settled on 2007 runtime.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)