• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

ColdFusion 10 - No MS Access with Unicode driver

New Here ,
Jun 04, 2013 Jun 04, 2013

Copy link to clipboard

Copied

I'm setting up a new server to test ColdFusion 10 (will be upgrading from 8) and I don't have the option for MS Access with Unicode from the driver list when adding a new DSN. Based on this referrence (http://help.adobe.com/en_US/ColdFusion/10.0/Admin/WSc3ff6d0ea77859461172e0811cbf364104-7fe6.html) it looks like it should still be included, but I'm not seeing it. Any ideas how to get the option back?

TOPICS
Database access

Views

2.5K

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
community guidelines
New Here ,
Dec 06, 2013 Dec 06, 2013

Copy link to clipboard

Copied

Hello IcePerson13,

  this is possible. However, it is only possible within the 32bit Version of ColdFusion on a 64bit OS and - amazingly - not in the standard ColdFusion 10 32bit setup routine on a 64bit OS. That there is no support for 64bit CF10 on a 64bit OS is likely due to the ODBC limitations.

The method is described at:

http://cfassociates.samuraiz.co.jp/index.cfm/faq/aboutcf/cf10-nosupport-msaccess-unicode/

(open this url in Google Chrome, which will then offer you automatically a reasonable translation).

The trick is, to install CF10 32bit on a 32bit OS, be it WinXP or whatever. Then pickup the izmjniado.dll from that machine at [cf10_root]/cfusion/lib. This is the dll which offers the connection "Microsoft Access with Unicode".

Then install CF10 32bit on your 64bit OS.

Then copy the izmjniado.dll to [cf10_root] / cfusion / lib on the 64bit machine you actually have installed the 32bit CF10 on (stop CF service before, of course). After restarting CF, the datasource option "Microsoft Access with Unicode" is already there, but will throw an error when you want to bind in a connection to a MSAccess database on your machine.

Then correct this error cause via editing neo-datasource.xml, by cleaning it up (first stop CF server and make a backup of the original file). Basically get rid of the "<char code="09">" strings in this xml file. No line break in the middle, one space between "Data" and "Source".

so before it looks like:

  • <var name='url'> <string> jdbc: izmado: Provider = Microsoft.Jet.OLEDB.4.0; Data <char code='0a'/> <char code='09'/> <char code = '09 '/> <char code='09'/> <char code='09'/> <char code='09'/> <char code='09'/> <char code='09'/> <char code = '09 '/> Source = C 😕 db / uriage.mdb; IzmJdbcEsc = yes; IzmReleaseOnClose = no <char code='0a'/> <char code='09'/> <char code = '09' /> <char code='09'/> <char code='09'/> <char code='09'/> <char code='09'/> <char code='09'/> </ string > </ var>

afterwards it should look like

  • <var name='url'> <string> jdbc: izmado: Provider = Microsoft.Jet.OLEDB.4.0; Data Source = C 😕 db / uriage.mdb; IzmJdbcEsc = yes; IzmReleaseOnClose = no </ string> </ var>

Then restart CF10 and there you are. We have it running wonderfully against Access with Unicode on a Win2012R, Apache 2.

Why Adobe Systems ignores this way a *large* part of its customers who need to use - be it only for legacy reasons - MSAccess with Unicode, remains a complete mistery for anyone thinking half way commercially. It is even more hallucinating because Adobe Systems itself declares in its specs that CF10 works with MSAccess containing Unicode strings (see: the CF10 specification document from Adobe itself, where Adobe solemly declares

"Connecting to Microsoft Access with Unicode" at http://help.adobe.com/en_US/ColdFusion/10.0/Admin/WSc3ff6d0ea77859461172e0811cbf364104-7fe6.html)/WS...). It may well be that this Unicode feature is not very relevant for the American market (the standard MSAccess driver does connect to MSAccess but does not deal with its Unicode strings), but it definitely is for the rest of the world.

Dealing like this with extremely popular Unicode enabled products feels like having been thrown back 10 years back in the ColdFusion development.

So, yes, this works. But Adobe should fix this immediately in its install routines.


Votes

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
community guidelines
New Here ,
Jan 09, 2014 Jan 09, 2014

Copy link to clipboard

Copied

Please vote on this bug https://bugbase.adobe.com/index.cfm?event=bug&id=3691289

It stops us from migrating from CF 9 to 10 as we of course don't have 32 servers anymore.

Votes

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
community guidelines
Community Expert ,
Jan 19, 2014 Jan 19, 2014

Copy link to clipboard

Copied

LATEST

+1 vote

Votes

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
community guidelines
Resources
Documentation