Highlighted

coldfusion16 and ODBC

Contributor ,
Jun 28, 2017

Copy link to clipboard

Copied

With Coldfusion11 , I can declare datasource as Access driver (.mdb)

my client bought coldfusion16  (as that is the actual version)

now, when declaring datasource as Access driver,

there is the error :

Connection verification failed for data source:

java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][Gestionnaire de pilotes ODBC] Source de données introuvable et nom de pilote non spécifié

The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][Gestionnaire de pilotes ODBC] Source de données introuvable et nom de pilote non spécifié

Even , after declaring the datasource in the ODBC32.exe Under  Windows/sysWOW64 

the error is still there.

No way to work again with Coldfusion16

is there a change between CF11 and CF16 with the ODBC driver ?

I need  URGENT  HELP  with this.

Is there another driver to use to make Access .mdb files to be datasource ?

Thanks, Pierre.

TOPICS
Advanced techniques

Views

327

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

coldfusion16 and ODBC

Contributor ,
Jun 28, 2017

Copy link to clipboard

Copied

With Coldfusion11 , I can declare datasource as Access driver (.mdb)

my client bought coldfusion16  (as that is the actual version)

now, when declaring datasource as Access driver,

there is the error :

Connection verification failed for data source:

java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][Gestionnaire de pilotes ODBC] Source de données introuvable et nom de pilote non spécifié

The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][Gestionnaire de pilotes ODBC] Source de données introuvable et nom de pilote non spécifié

Even , after declaring the datasource in the ODBC32.exe Under  Windows/sysWOW64 

the error is still there.

No way to work again with Coldfusion16

is there a change between CF11 and CF16 with the ODBC driver ?

I need  URGENT  HELP  with this.

Is there another driver to use to make Access .mdb files to be datasource ?

Thanks, Pierre.

TOPICS
Advanced techniques

Views

328

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
Jun 28, 2017 0

Have something to add?

Join the conversation