Provider=any oledb provider's name OledbKey1=someValue OledbKey2=someValue Will just pass on the connection string to the specified ODBC driver. Respective ODBC driver's connection strings options. Standard Security Driver= OdbcKey1=someValue OdbcKey2=someValue.In Access try options and choose 2007 encryption method instead. You are having problems, try change password to a short one with normalĮncrypted using Access 2010 - 2013 default encryption scheme does not Also that some characters might cause trouble. Some reports of problems with password longer Jet OLEDB:Database Password= MyDbPassword Provider= .12.0 Data Source= C:\myFolder\myAccessFile.accdb This is the connection string to use when you have an Access 2007 -Ģ013 database protected with a password using the "Set Database Standard security Provider= .12.0 Data Source= C:\myFolder\myAccessFile.accdb.
Is anything different with that? Sorry for the edits! What would be the advantage to 64 over 32 bit project? Any ideas on why the original developer would have done so? And can/how do I change it to 32?Įdit: eventually I will need to connect to an accdb. It has to be something about this project. So, I set up a new project to just have a button to connect to my data source and it works just fine. Also, if I try to change something on the fly, it tells me I can't make changes to a 64-bit application. It seems to change it to 4.9 when I run the project. That seems odd to me because I specify 4.0 but the error says 4.9. I get this error: The '.4.9' provider is not registered on the local machine. Is there something I'm missing? I saw in some searches something about a Windows pool and 32 bit versus 64 bit? To be honest I didn't really understand or maybe I just didn't read enough.ĭbProvider = "Provider=.4.0 "ĭbSource = "Data Source = C:\Example.mdb"Ĭon.ConnectionString = dbProvider & dbSource I just wrote a simple connection to start with.
The code that was in there using an ACE connection didn't work so I thought I'd fall back on my trusty Jet, but it isn't working either.
The long and short of it is that part of the project was supposed to check a field in an Access database (2013 if it matters).
I've mainly worked with old (yes out of date) VB 6 projects. I have inherited a VB.Net project from the original developer and I don't know much about.
0 kommentar(er)
