TheSwamp

Code Red => AutoLISP (Vanilla / Visual) => Topic started by: ElpanovEvgeniy on June 29, 2010, 10:04:10 AM

Title: ADODB.Connection windows7 (64)
Post by: ElpanovEvgeniy on June 29, 2010, 10:04:10 AM

if you line access to the database *. mdb from windows (64), please share.
My research:

Code: [Select]

   (setq ac (vlax-create-object "ADODB.Connection")
 ar (vlax-create-object "ADODB.Recordset")
    )
    (vlax-invoke-method
     ac
     "Open"
     "Database=D:\\technolog.mdb; Server=localhost; User ID=Admin; Password=;Provider=sqloled"
     "Admin"
     ""
     0
    ) ;_  vlax-invoke-method
  ==>> error provider

  
    (vlax-invoke-method
     ac
     "Open"
     "Driver={Microsoft Access Driver (*.mdb)};DBQ=D:\\technolog.mdb;"
     "Admin"
     ""
     0
    ) ;_  vlax-invoke-method
  ==>> error provider

  
    (vlax-invoke-method
     ac
     "Open"
     "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\\technolog.mdb;User Id=admin;Password=;"
     "Admin"
     ""
     0
    ) ;_  vlax-invoke-method
  ==>> error provider

  
    (vlax-invoke-method
     ac
     "Open"
     "Provider=SQLNCLI10;Data Source=D:\\technolog.mdb;Persist Security Info=False;"
     "Admin"
     ""
     0
    ) ;_  vlax-invoke-method
  ==>> error provider
    (vlax-invoke-method
     ac
     "Open"
     "Provider=SQLOLEDB;Data Source=D:\\technolog.mdb;"
     "Admin"
     ""
     0
    ) ;_  vlax-invoke-method
  ==>> SQL Server does not exist or permission denied.
help my.

Title: Re: ADODB.Connection windows7 (64)
Post by: kpblc on June 29, 2010, 12:32:03 PM

Evgeniy, look at http://www.theswamp.org/index.php?topic=33769.0

Title: Re: ADODB.Connection windows7 (64)
Post by: It's Alive! on June 29, 2010, 07:14:00 PM

I think access uses JET which does not work on 64bit  :|
You have three choices, move the .MDB to a .MDF/ SQL Express or other SQL server , transfer your data to SQLite or quit using databases

Title: Re: ADODB.Connection windows7 (64)
Post by: ElpanovEvgeniy on July 09, 2010, 05:48:12 AM

after installing ms office 2010 x64 can use the line call:

Code: [Select]

(strcat "Provider=Microsoft.ACE.OLEDB.12.0;Data Source="
           (findfile "technolog.mdb")
           ";Persist Security Info=False;"
   )another way - the driver installation from ms office 2010 x64
AccessDatabaseEngine_X64.exe   
28.1 MB (http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en)

Title: Re: ADODB.Connection windows7 (64)
Post by: Kerry on July 09, 2010, 05:51:44 AM

Quote from: ElpanovEvgeniy on July 09, 2010, 05:48:12 AM

after installing ms office 2010 x64 can use the line call:

Code: [Select]

(strcat "Provider=Microsoft.ACE.OLEDB.12.0;Data Source="
           (findfile "technolog.mdb")
           ";Persist Security Info=False;"
   )another way - the driver installation from ms office 2010 x64
AccessDatabaseEngine_X64.exe   
28.1 MB (http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en)

yes Evgeniy ,
but unfortunately you can't install the 64 bit driver if 32 bit office is installed ....
and most people will install the 32 bit so that their OLD add-ons will still work :- most aren't yet converted to 64bit :(

Title: Re: ADODB.Connection windows7 (64)
Post by: Kerry on July 09, 2010, 09:27:44 PM

In fact, from  http://technet.microsoft.com/en-us/library/ee681792.aspx

Quote

The recommendations for which edition of Office 2010 to install are as follows:

If users in your organization depend on existing extensions to Office, such as ActiveX controls, third-party add-ins, in-house solutions built on previous versions of Office, or 32-bit versions of programs that interface directly with Office, we recommend that you install 32-bit Office 2010 (the default installation) on computers that are running both 32-bit and 64-bit supported Windows operating systems.


If some users in your organization are Excel expert users who work with Excel spreadsheets that are larger than 2 gigabytes (GB), they can install the 64-bit edition of Office 2010. In addition, if you have in-house solution developers, we recommend that those developers have access to the 64-bit edition of Office 2010 so that they can test and update your in-house solutions on the 64-bit edition of Office 2010.

and
http://office.microsoft.com/en-au/word-help/choose-the-32-bit-or-64-bit-version-of-microsoft-office-HA010369476.aspx