Highlighted

accdb with CF9 under Win2008 R2 64bit

Explorer ,
Jan 27, 2012

Copy link to clipboard

Copied

Hi there

I have a accdb designed with Access 2010 64bit.

I am running CF9 under Win2008 R2 64bit.

I have also installed http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=13255

I have now googled and tried some dozen tricks to get this combination work:

until now - no way!

Does anybody succeed to to so and is there somewhere a description?

Thanx for help - Didi

Adobe Community Professional
Correct answer by BKBK | Adobe Community Professional

OK. That was that then. Let's move on.

I do believe our hopes now lie with JDBC. Since ColdFusion is a Java application, finding a 32-bit and 64-bit JDBC driver for MS Access will help many developers.

My search brought me to HXTT's JDBC driver for MS Access. The only problem is, I couldn't tell whether their driver is for 32-bit or 64-bit Access. Could it (hopefully) be universal, automatically detecting the system? 

(After the customary virus scan) I unpacked their access.zip file, copied the essential file Access_JDBC40.JAR from /access/lib/ to ColdFusion's lib directory. That's all there is to installing the driver. I then restarted ColdFusion.

I went to the ColdFusion Administrator and configured a datasource as follows:

Data Source Name: myAccessDSN

Driver: Other

JDBC URL: jdbc:access:/C:/Users/BKBK/Documents/myDB.accdb

Driver Class: com.hxtt.sql.access.AccessDriver

Driver Name: com.hxtt.sql.access.AccessDriver

It worked flawlessly. But then again, though I installed everything you did, I am on 32-bit Access. 

accessDSN.jpg

TOPICS
Database access

Views

26.0K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

accdb with CF9 under Win2008 R2 64bit

Explorer ,
Jan 27, 2012

Copy link to clipboard

Copied

Hi there

I have a accdb designed with Access 2010 64bit.

I am running CF9 under Win2008 R2 64bit.

I have also installed http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=13255

I have now googled and tried some dozen tricks to get this combination work:

until now - no way!

Does anybody succeed to to so and is there somewhere a description?

Thanx for help - Didi

Adobe Community Professional
Correct answer by BKBK | Adobe Community Professional

OK. That was that then. Let's move on.

I do believe our hopes now lie with JDBC. Since ColdFusion is a Java application, finding a 32-bit and 64-bit JDBC driver for MS Access will help many developers.

My search brought me to HXTT's JDBC driver for MS Access. The only problem is, I couldn't tell whether their driver is for 32-bit or 64-bit Access. Could it (hopefully) be universal, automatically detecting the system? 

(After the customary virus scan) I unpacked their access.zip file, copied the essential file Access_JDBC40.JAR from /access/lib/ to ColdFusion's lib directory. That's all there is to installing the driver. I then restarted ColdFusion.

I went to the ColdFusion Administrator and configured a datasource as follows:

Data Source Name: myAccessDSN

Driver: Other

JDBC URL: jdbc:access:/C:/Users/BKBK/Documents/myDB.accdb

Driver Class: com.hxtt.sql.access.AccessDriver

Driver Name: com.hxtt.sql.access.AccessDriver

It worked flawlessly. But then again, though I installed everything you did, I am on 32-bit Access. 

accessDSN.jpg

TOPICS
Database access

Views

26.0K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jan 27, 2012 0
Adobe Community Professional ,
Jan 30, 2012

Copy link to clipboard

Copied

1) Did you in every case add the following line to the Connection String field in the ColdFusion Administrator?

Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=path_to_mdb/accdb_file

2) Do you have any 32Bit MS Office applications installed on the server?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 30, 2012 0
Explorer ,
Jan 30, 2012

Copy link to clipboard

Copied

ad 1)  I try again

I guess it must be in the form c:\mypath\myDB.accdb

Backslashes, not forward slashes?

ad 2) nope

When I add a new Datasource in CFadmin, what Type of Driver do I select??

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 30, 2012 0
Adobe Community Professional ,
Jan 30, 2012

Copy link to clipboard

Copied

Didi wrote:

ad 1)  I try again

I guess it must be in the form c:\mypath\myDB.accdb

Backslashes, not forward slashes?

Your path OK.

When I add a new Datasource in CFadmin, what Type of Driver do I select??

MS Access

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 30, 2012 0
Explorer ,
Jan 30, 2012

Copy link to clipboard

Copied

Capture.GIF

Clicking Submit says ..

Unable to update the NT registry.

Variable DRIVERPATH is undefined.

And when I try to verify the datasource it says ..

Connection verification failed for data source: movo2direct

java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application

The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 30, 2012 0
Adobe Community Professional ,
Jan 31, 2012

Copy link to clipboard

Copied

Ah, I see. That is a well-known problem. Had you registered the system DSN yet?

In any case, let's start all over again. Delete everything from the Connection String field. The steps follow.

1) You'll have to start by registering the (MS Access) System DSN. To do so, double-click on the file c:\windows\SysWOW64\odbcad32.exe to launch it.

2) Select the tab System DSN and press Add. Select Microsoft Access Driver(*.mdb, *.accdb) and press Finish.

3) Give the datasource a name. (Jot it down, as it is the same datasource name you will have to use in the ColdFusion Administrator.) Now, double-click on the datasource  name (Alternatively,  press Configure.). You should now get an interface with which to add a database.

4) Press Select. Under the Directories: field, locate the directory in which you have stored your MDB or ACCDB file. The list of files in the directory should automatically appear in the field to the left.

5) Click on the database you require, and press OK. In so doing, you have coupled the database to the datasource.

6) Press OK, and again OK, to leave the ODBC interface.

7) Verify that Windows has created the right registry values. To do so, run Wndows' regedit on the command-prompt. You should have registry entries similar to the following:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\myAccessDSN\

    DBQ=C:\Users\BKBK\Documents\myDB.accdb

    Driver=C:\PROGRA~2\COMMON~1\MICROS~1\OFFICE14\ACEODBC.DLL

    DriverId=dword:00000019

    FIL=MS Access

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources\

    myAccessDSN=Microsoft Access Driver (*.mdb, *.accdb)

While configuring Windows ODBC, the name I gave for my datasource was myAccessDSN. That is also the name I am giving to the datasource in the Administrator. The location of my Access database is C:\Users\BKBK\Documents\myDB.accdb. That was it then.

After following the above procedure, I still got the following familiar error message when I attempted to verify the datasource in the Administrator:

Unable to update the NT registry.

Variable DRIVERPATH is undefined.

That is known to possibly be a bug. So I ignored it. I went ahead and ran a cfquery on the Access database. It worked!

Useful references:


Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 31, 2012 0
Explorer ,
Jan 31, 2012

Copy link to clipboard

Copied

There is no

Microsoft Access Driver(*.mdb, *.accdb)

ODBC-MdbOnly.GIF

CFadmin says

movo2odbc-err.GIF

Well, I will go and read the articles you cited, maybee this brings me further ...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 31, 2012 0
Adobe Community Professional ,
Feb 01, 2012

Copy link to clipboard

Copied

There is no Microsoft Access Driver(*.mdb, *.accdb)

You don't need to look any further. It is clear from your picture that you've only got the older versions of the drivers. Like you, I have versions 6.01.7600.17632. But I have also got versions 14.00.4760.1000, too.

Something must have gone wrong during your installation of the MS Access Database Engine 2010. Reinstall it.

If you encounter any problems installing the 64-bit version, then install the 32-bit version. Restart Windows(!) and follow the 7 steps I gave above.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 01, 2012 0
Explorer ,
Feb 01, 2012

Copy link to clipboard

Copied

I don't think, that the installation went wrong. I have done this several times yet and it never indicates any error.

Let me ask something else first :

I use myDB.accdb created  with  Access 2010 64bit. I would now guess, that the *.accdb is also 64bit - is that correct?

How can I verify that?

And further, that I need 64bit drivers?

As much as I understand from the articles you cited, "c:\windows\SysWOW64\odbcad32.exe" is meant for using 32bit drivers on a 64bit windows.

What we see are Version 6 drivers which I think are 32bit drivers. This seems consistet to the above.

So how could this work?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 01, 2012 0
Adobe Community Professional ,
Feb 02, 2012

Copy link to clipboard

Copied

From what you've said, we don't need to check. Your installation went smoothly. So, if you installed 64-bit, then you have 64-bit.

However, I am now of the opinion that, what you need in order to run Access, are the 32-bit drivers! Yes, the 32-bit, not the 64-bit, drivers! I would even wonder aloud: 64-bit MS Access 2010 may sometimes require only 32-bit drivers, for example, on an Operating System running certain Microsoft 32-bit applications like Office(and certain applications like ColdFusion). Notice how Microsoft themselves put the 32-bit binary odbcad32.exe in the 64-bit directory c:\windows\SysWOW64\. This means it also applies to 64-bit!

Of course, the gist of this all is that 32-bit software may run on a 64-bit Operating System like your Win2008. So, the Microsoft Access Driver (*.mdb, *.accdb) on my 64-bit Windows 7 must have come from my 32-bit installation of the MS Access Database Engine 2010.

A test worth doing is to uninstall the 64-bit Access 2010 engine, and install the 32-bit version. You cannot have both versions on the same machine.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 02, 2012 0
Explorer ,
Feb 02, 2012

Copy link to clipboard

Copied

Following the links you referenced I found the following information:

http://www.coldfusionmuse.com/index.cfm/2010/12/31/Access.on.64bit.ColdFusion

"

Here's the catch. Windows 64bit is capable of running 32bit software. You know this if you think about it. In fact the odbcad32.exe file above is a 32 bit control panel applet for managing 64 bit drivers. So the trick is to figure out how to manage 32bit drivers on your system. The good news is that the old version of the ODBC manager (the one that handles 32 bit drivers) still exists on your 64bit machine. Take a look in the %systemroot%/sysWOW64/ folder. You will see a version of the same file - odbcad32.exe. Open this control panel applet and you will discover that it actually manages the old list of 32 bit drivers. I know it's convoluted - a file in "system32" called odbcad32.exe manages 64 bit drivers while a file in the sysWOW64 folder manages 32 bit drivers. If you need to know, the "sysWOW64" folder stands for "Windows on Windows 64" - meaning plain old Windows 32 bit aps running on the Windows 64 bit platform.

"

This goes consistent with my following observation:

odbca-sys32 -14.GIF

so the Version 14 Drivers, which I assume are the newly installed 64bit drivers, show up in System32 🙂

Now one could think to be on the enlighted path ... nope!

Connecting CF9 to a such created System DNS says :

movo-odbc64-mismatch.GIF

Life ain't easy  ...

Well, looking on a solution before I stumbled over this forum I have everywhere found the information, that *.accdb created with  DO NEED 64bit drivers.

That's why I installed AccessDatabaseEngine_x64.exe.

Question: How can I find out, whether my .accdb is 32bit  or 64bit ???

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 02, 2012 0
Adobe Community Professional ,
Feb 02, 2012

Copy link to clipboard

Copied

Here's the catch. Windows 64bit is capable of running 32bit software. You know this if you think about it. In fact the odbcad32.exe file above is a 32 bit control panel applet for managing 64 bit drivers. So the trick is to figure out how to manage 32bit drivers on your system. The good news is that the old version of the ODBC manager (the one that handles 32 bit drivers) still exists on your 64bit machine. Take a look in the %systemroot%/sysWOW64/ folder. You will see a version of the same file - odbcad32.exe. Open this control panel applet and you will discover that it actually manages the old list of 32 bit drivers

Indeed. That was also what I observed.

I know it's convoluted - a file in "system32" called odbcad32.exe manages 64 bit drivers while a file in the sysWOW64 folder manages 32 bit drivers. If you need to know, the "sysWOW64" folder stands for "Windows on Windows 64" - meaning plain old Windows 32 bit aps running on the Windows 64 bit platform.

I don't find it convoluted at all. I, too, came across the meaning of WOW64. In fact, I am surprised that, having discovered what it stands for, you still went ahead and used the binary odbcad32.exe in System32 rather than the version in SysWOW64! That is why you got this error: "The specified DSN contains an architecture mismatch between the Driver and Application".

In any case, that error message also tells me that your ACCDB file may be 64-bit. Again, for the purposes of creating Microsoft Access DSN in ColdFusion, you will need to create a 32-bit System DSN using this 32-bit application: c:\windows\SysWOW64\odbacd32.exe.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 02, 2012 0
Explorer ,
Feb 02, 2012

Copy link to clipboard

Copied

Let me explain why I hesitate to deinstall AccessDatabaseEngine_x64.exe and install the 32-Engine:

Actually I have found a way to get to the data in my *.accdb by linking it to SQLServer 2008 R2 Express.

This works if AccessDatabaseEngine_x64.exe is installed, since nly then it finds the following Provider

express-Provider.GIF

However, for several reasons I do not like this approach.

Rather I would like a 'direct' mounting as we discussed it above.

Of course I fear to loose my linked db when I deinstall AccessDatabaseEngine_x64.exe 😞

One (more) thing  I do not understand:

In SQL Express it says version 12.0 whereas in the system32\adbcad32.exe it says 14.0

Why is this?

Which version is the one that works with you?

Mystery over mystery ...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 02, 2012 0
Adobe Community Professional ,
Feb 03, 2012

Copy link to clipboard

Copied

12 and 14 are the names that Microsoft's developers gave under the hood for, respectively, Office 2007 and Office 2010. So, where you see version 12.0, Microsoft Office 2007 Access is being implied. Where you see version 14.0, Microsoft Office 2010 Access is being implied. You appear to have both Access versions installed. Could it be that you are mixing up the version 12.0 driver with the version 14.0 Access?

Besides Office version, the other main consideration is Bitness. On 64 bit Windows, such as yours, 64 bit applications are stored in Program Files (Progra~1, for short), and 32 bit applications are stored in Program Files (x86) (Progra~2, for short). Furthermore, the Windows system directory for 32-bit files is C:\Windows\SysWOW64, and the Windows system directory for 64 bit files is C:\Windows\System32.

64 bit Windows can handle 32 bit as well as 64 bit versions of an application. However, it's all down to how you put your configuration together.

The driver for Access has the same name in Office 2007(v. 12.0) and in Office 2010 (v. 14.0), which is, ACEODBC.DLL. The location of that driver will be as follows, depending on whether the Office version is 32 bit or 64 bit:

32 bit Office 2007: C:\PROGRA~2\COMMON~1\MICROS~1\OFFICE12\ACEODBC.DLL

64 bit Office 2007: C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\ACEODBC.DLL

32 bit Office 2010: C:\PROGRA~2\COMMON~1\MICROS~1\OFFICE14\ACEODBC.DLL

64 bit Office 2010: C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE14\ACEODBC.DLL

I'll illustrate using my own case. I have 32-bit Microsoft Office 10. The Access driver my system uses is therefore C:\PROGRA~2\COMMON~1\MICROS~1\OFFICE14\ACEODBC.DLL. Scroll up to the 7 steps I gave above. You will see that that is indeed the value of the driver in my Windows registry. You, too, should verify your registry entries.

How did I configure the Access System DSN? By following the 7 steps above. My Office version is 32-bit, so I used C:\Windows\SysWOW64\odbcad.exe. If your Office version is 64 bit, then you should use C:\Windows\System32\odbcad.exe instead.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Explorer ,
Feb 03, 2012

Copy link to clipboard

Copied

ok, I finally did it!

Fortunately, my server is running as a VM on ESX. So I took a snapshot, deinstalled the AccessDatabaseEngine_x64.exe and installed AccessDatabaseEngine.exe.

Then I configured in SysWOW64\odbacd32.exe a DSN with the v14.0 Provider.

I think this is exactly what you meant by .. ?

In any case, that error message also tells me that your ACCDB file may be 64-bit. Again, for the purposes of creating Microsoft Access DSN in ColdFusion, you will need to create a 32-bit System DSN using this 32-bit application: c:\windows\SysWOW64\odbacd32.exe.

Next: In CFadmin I added two datasources: one via odbc (movo2odbc), one directly with acces (movo2accdb):

Well, my data-coffin says:

WithALE32.GIF

Do you have this running under the same configuration ( CF9 under Win2008 R2 64bit ) ?

----------------------------

hi, we just crossed posting .. this one is done without reading the previous one. I will do so instantly ..

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Explorer ,
Feb 03, 2012

Copy link to clipboard

Copied

How did I configure the Access System DSN? By following the 7 steps above. My Office version is 32-bit, so I used C:\Windows\SysWOW64\odbcad.exe. If your Office version is 64 bit, then you should use C:\Windows\System32\odbcad.exe instead.

ok, once again with

C:\Windows\System32\odbcad.exe

...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Explorer ,
Feb 03, 2012

Copy link to clipboard

Copied

Hi there

first of all: thousand thanx of taking care of my problem !!!

Most things you say  I understand, but some still confuses me.

ok, on my server, no MSO is installed at all. The my.accdb is created on a Win7 64 bit  with MSO 2010 64bit - no doubt about that!

Then I copied it to the server (Win2008 R2 64bit)

some puzzles remain ..

Since my MSO is 64 I tried now (having installed AccessDatabaseEngine.exe ) C:\Windows\System32\odbcad.exe

odbcadALE32Sys32.GIF

Hmmmm ...where are the drivers?

-----------------------

C:\Windows\SysWOW64\odbcad.exe on the other hand says ..

odbcadALE32SysWow64.GIF

???

-------------

one more thing:

As you can see from earlier Screenshots: when neither AccessDatabaseEngine_x64.exe nor AccessDatabaseEngine.exe is installed,

I don't see either the v12-Provider in SQL server nor the v14-Driver in odbacd32.exe.

So it's AccessDatabaseEngine_x64.exe who introduces both drivers at setup.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Explorer ,
Feb 03, 2012

Copy link to clipboard

Copied

How did I configure the Access System DSN? By following the 7 steps above. My Office version is 32-bit, so I used C:\Windows\SysWOW64\odbcad.exe. If your Office version is 64 bit, then you should use C:\Windows\System32\odbcad.exe instead.

One more question:

I have a 64-bit Office with which I create a my.accdb, then I copy it to a 64bit server.

Why do I need to install AccessDatabaseEngine.exe and not AccessDatabaseEngine_x64.exe ?

That's absolutely confusing to me ....

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Adobe Community Professional ,
Feb 03, 2012

Copy link to clipboard

Copied

Didi wrote:

ok, on my server, no MSO is installed at all. The my.accdb is created on a Win7 64 bit  with MSO 2010 64bit - no doubt about that!

Then I copied it to the server (Win2008 R2 64bit)

I would assume that Windows installs Microsoft Access 2010 as a Microsoft Office 2010 application. OK, yours is 64 bit. Did you install the 64 bit AccessDatabaseEngine_x64.exe on Win2008? My guess is that you should

some puzzles remain ..

Since my MSO is 64 I tried now (having installed AccessDatabaseEngine.exe ) C:\Windows\System32\odbcad.exe

A mistake. AccessDatabaseEngine.exe is 32 bit, and so you require C:\Windows\SysWOW64\odbcad.exe for it.

I have a 64-bit Office with which I create a my.accdb, then I copy it to a 64bit server.

Why do I need to install AccessDatabaseEngine.exe and not AccessDatabaseEngine_x64.exe ?

You don't need to. To keep everything to 64 bit, you should install AccessDatabaseEngine_x64.exe! However, as I said before, it's all about 2 things: driver version and bitness. If you wish to run  applications that require 32-bit Access drivers, you should install AccessDatabaseEngine.exe instead.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Explorer ,
Feb 03, 2012

Copy link to clipboard

Copied

Well, lucky boy who has a snapshot 🙂

Now I am back at the point where I entered this thread, but now with a more precise description of what I am doing:

  1. I have a 64-bit Office on a Win 7 64bit Workstation, with which I create a my.accdb.
  2. Then I copy it to a server running CF9 under Win2008 R2 64bit..
  3. I have installed AccessDatabaseEngine_x64.exe
  4. I use  C:\Windows\System32\odbcad.exe
  5. Creating a DSN it offers me v14.0 drivers
  6. Adding a new Datasource in CFadmin says:

movo-odbc64-mismatch.GIF

But at least we seem now to agree, that both of us assume that I am doing the right thing? Don't we?

Or do I still miss something?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Guide ,
Feb 03, 2012

Copy link to clipboard

Copied

Are you sure you *really* want to go through all this just to use Access...?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Adobe Community Professional ,
Feb 03, 2012

Copy link to clipboard

Copied

Didi wrote:

Well, lucky boy who has a snapshot 🙂

Now I am back at the point where I entered this thread, but now with a more precise description of what I am doing:

  1. I have a 64-bit Office on a Win 7 64bit Workstation, with which I create a my.accdb.
  2. Then I copy it to a server running CF9 under Win2008 R2 64bit..
  3. I have installed AccessDatabaseEngine_x64.exe
  4. I use  C:\Windows\System32\odbcad.exe
  5. Creating a DSN it offers me v14.0 drivers
  6. Adding a new Datasource in CFadmin says:

movo-odbc64-mismatch.GIF

But at least we seem now to agree, that both of us assume that I am doing the right thing? Don't we?

Or do I still miss something?

I missed 2 things. You mentioned nothing about uninstalling the 32 bit engine nor about the registry.

Uninstall AccessDatabaseEngine.exe. Restart Win2008. (Re)Install AccessDatabaseEngine_x64.exe.

Corresponding to the above, the 7 steps for 64 bit Microsoft Access 2010 are:

1) You'll have to start by registering the (MS Access) System DSN. To do so, double-click on the file c:\windows\System32\odbcad32.exe to launch it.

2) Select the tab System DSN and press Add. Select Microsoft Access Driver(*.mdb, *.accdb) and press Finish.

3) Give the datasource a name. (Jot it down, as it is the same datasource name you will have to use in the ColdFusion Administrator.) Now, double-click on the datasource  name (Alternatively,  press Configure.). You should now get an interface with which to add a database.

4) Press Select. Under the Directories: field, locate the directory in which you have stored your MDB or ACCDB file. The list of files in the directory should automatically appear in the field to the left.

5) Click on the MDB or ACCDB database you require, and press OK. In so doing, you have coupled the database to the datasource.

6) Press OK, and again OK, to leave the ODBC interface.

7) Verify that Windows has created the right registry values. To do so, run Wndows' regedit on the command-prompt. You should have registry entries similar to the following:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\myAccessDSN\

    DBQ=C:\Users\BKBK\Documents\myDB.accdb

    Driver=C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE14\ACEODBC.DLL

    DriverId=dword:00000019

    FIL=MS Access

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources\

    myAccessDSN=Microsoft Access Driver (*.mdb, *.accdb)

In this configuration, myAccessDSN is the name I give for my datasource. You should see your own instead. MyAccessDSN is also the name I would give to the datasource in the Administrator. The location of my Access database is C:\Users\BKBK\Documents\myDB.accdb. That was it then.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Explorer ,
Feb 03, 2012

Copy link to clipboard

Copied

BKBK wrote:

I missed 2 things. You mentioned nothing about uninstalling the 32 bit engine nor about the registry.

Uninstall AccessDatabaseEngine.exe. Restart Win2008. (Re)Install AccessDatabaseEngine_x64.exe.

There is not need to uninstall AccessDatabaseEngine.exe since I reverted my ESX VM back to a snapshot with my original setup ( CF9 under Win2008 R2 64bit plus AccessDatabaseEngine_x64.exe )

BKBK wrote:

Corresponding to the above, the 7 steps for 64 bit Microsoft Access 2010 are:

1) You'll have to start by registering the (MS Access) System DSN. To do so, double-click on the file c:\windows\System32\odbcad32.exe to launch it.

2) Select the tab System DSN and press Add. Select Microsoft Access Driver(*.mdb, *.accdb) and press Finish.

3) Give the datasource a name. (Jot it down, as it is the same datasource name you will have to use in the ColdFusion Administrator.) Now, double-click on the datasource  name (Alternatively,  press Configure.). You should now get an interface with which to add a database.

4) Press Select. Under the Directories: field, locate the directory in which you have stored your MDB or ACCDB file. The list of files in the directory should automatically appear in the field to the left.

5) Click on the MDB or ACCDB database you require, and press OK. In so doing, you have coupled the database to the datasource.

6) Press OK, and again OK, to leave the ODBC interface.

7) Verify that Windows has created the right registry values. To do so, run Wndows' regedit on the command-prompt. You should have registry entries similar to the following:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\myAccessDSN\

    DBQ=C:\Users\BKBK\Documents\myDB.accdb

    Driver=C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE14\ACEODBC.DLL

    DriverId=dword:00000019

    FIL=MS Access

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources\

    myAccessDSN=Microsoft Access Driver (*.mdb, *.accdb)

In this configuration, myAccessDSN is the name I give for my datasource. You should see your own instead. MyAccessDSN is also the name I would give to the datasource in the Administrator. The location of my Access database is C:\Users\BKBK\Documents\myDB.accdb. That was it then.

Exactly what I have done - step by step ..

reg-all64.GIF

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 03, 2012 0
Adobe Community Professional ,
Feb 04, 2012

Copy link to clipboard

Copied

You and I have gone as far as we can. My conclusion is that, when you install an MS Access datasource in the ColdFusion Administrator, ColdFusion uses a 32-bit application, macromedia.jdbc.MacromediaDriver, in the process.

To see this, run the following code (using your own admin password):

<cfset adminLogin=createobject("component","CFIDE.adminapi.administrator").login("my_cf_admin_pw")>

<cfset ds=createobject("component","CFIDE.adminapi.datasource")>

<cfdump var="#ds.setMSAccess#" >

This shows that the driver class is macromedia.jdbc.MacromediaDriver. In fact, the following code will let you see even further.

<cfset macromediaDriver=createobject("java","macromedia.jdbc.MacromediaDriver")>

<cfdump var="#macromediaDriver#" >

Macromedia.jdbc.MacromediaDriver is actually a legacy engine for setting the appropriate driver for a collection of databases, namely for DB2, Informix, MySQL, and so on. One of them, SequeLink, is for MS Access. I do believe that this construction is 32-bit, hence the incompatibility.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 04, 2012 0
Explorer ,
Feb 04, 2012

Copy link to clipboard

Copied

<cfset adminLogin=createobject("component","CFIDE.adminapi.administrator").l ogin("my_cf_admin_pw")>

<cfset ds=createobject("component","CFIDE.adminapi.datasource")>

<cfdump var="#ds.setMSAccess#" >

setMSaccess.GIF

<cfset macromediaDriver=createobject("java","macromedia.jdbc.MacromediaDrive r")>

<cfdump var="#macromediaDriver#" >

macromediadriver.GIF

Macromedia.jdbc.MacromediaDriver is actually a legacy engine for setting the appropriate driver for a collection of databases, namely for DB2, Informix, MySQL, and so on. One of them, SequeLink, is for MS Access. I do believe that this construction is 32-bit, hence the incompatibility.

This means no chance? 

----------------------

Another idea:

Would you give a chance to something like that?

url="jdbc:odbc:MyAccessDB"

className="sun.jdbc.odbc.JdbcOdbcDriver"

I did not find any information yet, whether 64bit is supported.

I used something like that many years ago, at that time it was for sur not 64bit.

--------

Or maybe even better something like that:

"jdbc:odbc:DRIVER=Microsoft Access Driver (*.mdb, *.accdb);DBQ=C:\\Northwind.accdb;PWD=1L0v3Acce55;"

Does this make sense? And how do I teach CF9 to use the correct driver?

(Ref:   http://msdn.microsoft.com/en-us/library/ff965871.aspx#DataProgrammingWithAccess2010_JDBCODBCExample )

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 04, 2012 0
Adobe Community Professional ,
Feb 08, 2012

Copy link to clipboard

Copied

That would in fact be my suggestion now: download and install an appropriate legacy 64 bit JDBC-ODBC driver.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 08, 2012 0
Guide ,
Feb 08, 2012

Copy link to clipboard

Copied

BKBK wrote:

That would in fact be my suggestion now: download and install an appropriate legacy 64 bit JDBC-ODBC driver SQL Server Express.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 08, 2012 0
Adobe Community Professional ,
Feb 08, 2012

Copy link to clipboard

Copied

Owain North wrote:

BKBK wrote:

That would in fact be my suggestion now: download and install an appropriate legacy 64 bit JDBC-ODBC driver SQL Server Express.

Point taken. However, mine is not to wonder why Access.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 08, 2012 0
Explorer ,
Mar 24, 2012

Copy link to clipboard

Copied

hi there

I would follow up on this thread since it perfectly documents the background.

Let's summarize: with http://www.hxtt.com/access.html and BKBK's support we now have a working environment.

One thing puzzles us:

The following steps work fine:

  1. SELECT qry from CF9 to the  DS
  2. UPDATE DS from CF9
  3. SELECT qry from CF9 to the DS (this reflects the change made in the step before)

But this procedure does not work

  1. SELECT qry from CF9 to the  DS
  2. UPDATE the underlying table from within MS Access
  3. SELECT qry from CF9 to the  DS (this does NOT reflect the change made in the step before)

What we already tried:

  • CFOBJECTCACHE does not help.
  • Setting "" in CFadmin does not help.
  • Disabling "Maintain Connections" in the Datasource does not help (see below).

hxtt-1.GIF

Anybody a helpful idea?  (A recommendation to change the database is NOT regarded as helpful )

-Didi

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Guide ,
Mar 24, 2012

Copy link to clipboard

Copied

A recommendation to change the database is NOT regarded as helpful

Dammit, that's me out then.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Adobe Community Professional ,
Mar 24, 2012

Copy link to clipboard

Copied

Procedure 1:

  1. SELECT qry from CF9 to the  DS
  2. UPDATE something in DS from CF9
  3. UPDATE something else in the underlying table from within MS Access
  4. SELECT qry from CF9 to the  DS

Procedure 2:

  1. SELECT qry from CF9 to the  DS
  2. UPDATE something in the underlying table from within MS Access
  3. UPDATE something else in DS from CF9
  4. SELECT qry from CF9 to the  DS

Does these procedures work? That is, does step 4 reflect both changes made in steps 2 and 3?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 1
Community Beginner ,
Mar 24, 2012

Copy link to clipboard

Copied

>>JDBC URL: jdbc:access:/C:/Users/BKBK/Documents/myDB.accdb

>But this procedure does not work

>    SELECT qry from CF9 to the  DS

>    UPDATE the underlying table from within MS Access

>    SELECT qry from CF9 to the  DS (this does NOT reflect the change made in the step before)

You need lockType=ACCESS connection property, then HXTT Access and MS Access can see each other.

For instance,  JDBC URL: jdbc:access:/C:/Users/BKBK/Documents/myDB.accdb?lockType=ACCESS

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 1
Adobe Community Professional ,
Mar 24, 2012

Copy link to clipboard

Copied

HXTT Support wrote:

>>JDBC URL: jdbc:access:/C:/Users/BKBK/Documents/myDB.accdb

>But this procedure does not work

>    SELECT qry from CF9 to the  DS

>    UPDATE the underlying table from within MS Access

>    SELECT qry from CF9 to the  DS (this does NOT reflect the change made in the step before)

You need lockType=ACCESS connection property, then HXTT Access and MS Access can see each other.

For instance,  JDBC URL: jdbc:access:/C:/Users/BKBK/Documents/myDB.accdb?lockType=ACCESS

Wow! HXTT Support! What a privilege!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Explorer ,
Mar 24, 2012

Copy link to clipboard

Copied

BKBK:

good idea to isolate the problem! -Thanx for the input!

HXTT Support:

Even better - now it works - triple Thanx for the solution!

hxtt-2.GIF

For those who recommend to change the DB (Owain, are you still there?   😞

We made some performance tests and compared 'accdb plus HXTT' with SQL 2008 Express.

'accdb plus HXTT' is incredibly fast. Regarding our application you cannot measure a difference in response time ..

-Didi

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Guide ,
Mar 24, 2012

Copy link to clipboard

Copied

When you have one user and all the files are already cached, maybe

Wait for a second user to hit your site, it'll be like a DDOS.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Explorer ,
Mar 24, 2012

Copy link to clipboard

Copied

Owain North wrote:

When you have one user and all the files are already cached, maybe

Wait for a second user to hit your site, it'll be like a DDOS.

I absolutely agree, that accdb is not intended for a huge multiuser environment.

However, ColdFusion is the only user.

Since more than a decade I am told to trash MDBs since they will not perform.

On the other hand I have applications with half a million hits per day that do not even twinkle between two requests. Otherwise students learning for exam would rub through my doormat

As soon as performance drops, I definitely change ..

Besides some legacy stuff I can't get rid off on the fast lane (we have applications running from the 90s),  I somehow have started to regard this discussion about the lousy performing mdb as a kind of intellectual challenge

-Didi

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Community Beginner ,
Mar 24, 2012

Copy link to clipboard

Copied

>   When you have one user and all the files are already cached, maybe

First, according to one customer's random access( which needn't  cached for recycle) report for  big file on CD-R, HXTT Access engine is faster than MS Access ODBC engine.

Secondly, on lockType=ACCESS mode, HXTT Access won't use cache, since MS Access and HXTT Access can't share cache for concurrent according to old MS Access lock mechanism. HXTT Access has a faster data format parser/loader, and can utilize existent index fully for most sql.

Thirdly, only without lockType=ACCESS mode, HXTT Access can use multi-level cache, for physical file, object query reslut, session, transaction. All core is smaller, and HXTT Access can run on mobile platform.

Forth, only with assigned delayecClose connection property, HXTT Access can choose to build temporary index for big table without existent index.

According to performance test, HXTT drivers is faster than most of popular databases.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Explorer ,
Mar 24, 2012

Copy link to clipboard

Copied

HXTT Support wrote:

>   When you have one user and all the files are already cached, maybe

First, according to one customer's random access( which needn't  cached for recycle) report for  big file on CD-R, HXTT Access engine is faster than MS Access ODBC engine.

Secondly, on lockType=ACCESS mode, HXTT Access won't use cache, since MS Access and HXTT Access can't share cache for concurrent according to old MS Access lock mechanism. HXTT Access has a faster data format parser/loader, and can utilize existent index fully for most sql.

Thirdly, only without lockType=ACCESS mode, HXTT Access can use multi-level cache, for physical file, object query reslut, session, transaction. All core is smaller, and HXTT Access can run on mobile platform.

Forth, only with assigned delayecClose connection property, HXTT Access can choose to build temporary index for big table without existent index.

According to performance test, HXTT drivers is faster than most of popular databases.

aha!

So,

        jdbc:access:/C:/Users/BKBK/Documents/myDB.accdb?lockType=ACCESS

is ok for a developer environment.

So, what configuration would you (HXTT Support, not you Owain ) recommend for a productive installation?

       jdbc:access:/C:/Users/BKBK/Documents/myDB.accdb? ... delayedClose .. maxCacheSize .. lockTimeout.. etc. ???

Is this for CF9 still valid as for CF6.1 (as stated in your FAQ)?:

       ?delayedClose=15;maxCacheSize=6144;lockTimeout=2000

-Didi

PS: hey Owain, do not misunderstand me, it's not personal, just the challenge I mentioned above


Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Community Beginner ,
Mar 26, 2012

Copy link to clipboard

Copied

>So, what configuration would you (HXTT Support, not you Owain ) recommend for a productive installation?

It's only a jdbc url demo. You need only lockType=ACCESS since you need MS Access concurrent access. You can add other connection property if you need some special feature, for instance, ODBCTrimBehavior or caseInsensitive.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 26, 2012 0
Explorer ,
Mar 24, 2012

Copy link to clipboard

Copied

@ HXTT Support: are you still with us?

As instructed by BKBK I installed the driver-library to

  "C:\ColdFusion\lib\Access_JDBC40.jar"

However, when I replace Access_JDBC40.jar with the newer version Access_JDBC41.jar that was included with the package I received from you, it does not work.

Do I need to configure a different Driver Class or JDBC URL ?

Well, Access_JDBC40.jar works fine for me, but I guess, 41 has some advantages?

-Didi

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Community Beginner ,
Mar 24, 2012

Copy link to clipboard

Copied

>Well, Access_JDBC40.jar works fine for me, but I guess, 41 has some advantages?

You cannot use Access_JDBC41.jar, since JDBC 41 API is for JDK1.7.X, and your ColdFusion is using JDK1.6.X. Both of Access_JDBC40.jar and Access_JDBC41.jar are released as v5.1 for different JDBC API standard.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 1
Explorer ,
Mar 24, 2012

Copy link to clipboard

Copied

HXTT Support wrote:

You cannot use Access_JDBC41.jar, since JDBC 41 API is for JDK1.7.X, and your ColdFusion is using JDK1.6.X. Both of Access_JDBC40.jar and Access_JDBC41.jar are released as v5.1 for different JDBC API standard.

Thanx!!!

-Didi

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 24, 2012 0
Most Valuable Participant ,
Jul 19, 2012

Copy link to clipboard

Copied

Hi Didi,

For MSAccess in 64-bit CF, you need the 32-bit drivers.

Please follow these exact steps on the Win2008 R2 64bit CF9 machine:

1) Install the 32-bit AccessDatabaseEngine.exe.  Note: If 64-bit AccessDatabaseEngine_x64.exe or any 64-bit MS Office Apps are already installed, then AccessDatabaseEngine.exe must be installed via the command line with the "/passive" argument (ex: AccessDatabaseEngine.exe /passive).

2) Create DSN via CF Admin and ignore this error: "Unable to update the NT registry. Variable DRIVERPATH is undefined."

3) Register a "System DSN" using same name as in Step 2, via 32-bit C:\Windows\SysWOW64\odbcad32.exe, and choose this driver: "Microsoft Access Driver (*.mdb, *.accdb)"

Thanks,

-Aaron

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 19, 2012 0
Participant ,
Jul 22, 2012

Copy link to clipboard

Copied

Aaron,

    I followed your instructions above however I don't see the MDB db driver (at least that's what I named it when I created it in the SysWOW64)  so how do I make the "MDB" driver show in my CF Administrator DSN dropdown?

Connection verification failed for data source: MBD

java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: Data source name not found and no default driver specified

The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: Data source name not found and no default driver specified

Thanks,

Daren

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 22, 2012 0
Most Valuable Participant ,
Jul 22, 2012

Copy link to clipboard

Copied

Hi Daren,

Step 2 was: 'Register a "System DSN"' (not "User DSN").  And that drop down on "CF Admin > Data sources" displays drivers, not data sources.  Here are the steps to correct the MSAccess/x64CF issue:

1) Open C:\Windows\SysWOW64\odbcad32.exe

2) Click the "User DSN" tab

3) Select your data source (which you've named "MDB") and click "Remove"

4) Click the "System DSN" tab

5) Important: If your "MDB" data source exists here as well, then select it and click "Remove"

6) While still on the "System DSN" tab, add the "MDB" data source

Basically, your data source must be deleted from SysWOW64's odbcad32.exe on both the User DSN tab and the System DSN tab.  THEN, once it doesn't exist on either tab, it can be added on the System DSN tab.

Thanks,

-Aaron

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 22, 2012 0
Participant ,
Jul 27, 2012

Copy link to clipboard

Copied

Aaron,

    I'm still having an issue...apparently I'm not smarter than the equipment I'm using. Here's what I did:

  1. I opened the C:\Windows\SysWOW64\odbcad32.exe and removed my old DSN under the "User DSN" tab
  2. Opened hte "System DSN"
  3. DSN = MBD
  4. System Database I selected "Database“ and mapped it to my MBD.mdb database
  5. Opened CF Administrator
  6. Under "Ädd New Data Source" I typed MDB
  7. Under "Driver" selected "MS Access"
  8. Clicked "Add"
  9. In "Database File" I mapped to my MBD.mdb (still receive error) and received the following error: (Connection verification failed for data source: MBD
    java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][SequeLink Server]Unable to retrieve error message from backend ODBC Driver.
    The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][SequeLink Server]Unable to retrieve error message from backend ODBC Driver.)

9a. In "System Database File" I mapped to my MBD.mdb (still receive error) and received the same error.

When I go to my CF pages that pull data from the database I receive the following error: [Macromedia][SequeLink JDBC Driver][SequeLink Server]Unable to retrieve error message from backend ODBC Driver.

Any idea what I’m doing wrong?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 27, 2012 0