If you're looking for connection string syntax, you can find it here:
http://www.carlprothman.net/Default.aspx?tabid=90#ODBCDriverForAccess.
If you're new to Access, you should be aware that Access (Jet)
security is considered to be an oxymoron. It was cracked a long time
ago and offers no real protection. If you google it, you'll get
thousands of hits offering products and services to help you bypass
it. Access security is only good for deterring people who either have
no bad intentions or else are too dumb to know how to search the
Internet. For many developers, it's just not worth the hassle.
--Mary
On Mon, 21 Aug 2006 11:09:53 +0100, "Edwin Hannan"
<edwin.hannan_AT_NOSPAM_ntlworld.com> wrote:
[Quoted Text] >Hi All
>
>I am new to connecting MS Access and SQL databases so hope you all dont
>mind me posting an
>access related question:-)
>
>I use the following dsnLess connection string to connect to a access 2000
>mdb that is not secured. (I use Clarion as a Front End)..this connects me to
>the
>mdb no problem.
>
>I have a Global varaible AccessDBsource in the owner field of the table in
>my Table
>Definition which I assign the following connection string.
>
> AccessDBsource = 'DRIVER={{Microsoft Access Driver (*.mdb)}' |
> & ';DBQ=YourMdbFile' |
> & ';UID=admin' |
> & ';PWD=YourPasswordIfAny' |
> & ';ImplicitCommitSync=Yes' |
> & ';UserCommitSync=Yes' |
> & ';ExtendedAnsiSql=1' |
> & ';Threads=4' |
> & ';PageTimeout=5' |
> & ';MaxScanRows=8' |
> & ';MaxBufferSize=2048' |
> & ';FIL=MS Access'
>
>I know the name and location of the Secured.mdw that holds the workgroup
>info (users and passwords etc...) and I know all the passwords etc...
>
>The actual mdb does not have a password, so access must be via authorised
>uid and pw as per the Secured.mdw
>
>What do I add to the connection string to get me in?
>
>cheers
>
>Ed
|