ODBC JDBC Bridge

[jim-nih]

We are setting up a new server for CF MX7 and having a problem connecting to a
Remedy (AR System)database. There is no problems using the Remedy driver on
CF 5, but when using the same driver on MX7 we get a "driver not capable" error
message and a vendorerrcode of 9010 and sqlstate of HY000. Apparently an
odbc-jdbc bridge is needed to get this to work. We are checking with Remedy,
but if we have no success, has anyone experienced this and have you resolved it?

[MikerRoo]

Don't know if this will help your problem, but there is a hotfix updating the JDBC drivers.

More information at: [url]http://www.macromedia.com/go/1a3c2ad0[/url]

Good luck,
-- MikeR

[jim-nih]

I tried this but it didn't help. Thanks, however, for the suggestion. At least the updated drivers did not break anything else.

[AN Schwartz]

I am having a similar JDBC problem with the ODBC drivers that are supplied with
a database product called SmartWare. The error message is:

[Macromedia][SequeLink JDBC Driver][ODBC Socket][SmartWare Software][SmartWare
ODBC Driver]Driver not capable

One of the people at the SmartWare company wrote the following:

"I have talked to John about this and unequivocally, Cold Fusion is making a
request to a standard high level ODBC driver (SmartWare) and Cold Fusion is not
handling the feature anomaly correctly. In this case, the feature request could
be a simple as: is a cursor supported in some unique way. Anytime a client (in
this case Cold Fusion) makes an ODBC call that is not
supported, it should never shut down. Ever. In John's opinion, this release of
Cold Fusion is not complying with accepted ODBC standards in how it is handling
the anomaly, and especially in how it is responding. We are industry compliant.
Cold Fusion needs some work to meet this simple, Microsoft standard that we
comply with. Further, under no circumstances would John use CF. They have at
least one and probably more squirrels running under the covers. This is a bug
that we have not made, we follow industry standards and CF has a problem. A
software that does not work is not powerful, it is broken.
And it is not our responsibility to adhere to standards dictated by a broken
software. An ODBC / JDBC driver that does not report the error and shuts down
is more than a risk, it is a menace to commerce. So at some point we will get
around to looking at what is happening but this is a don't hold your breath
because it is off our radar."

From the tone of this message, I somehow suspect I will not get much help from
the SmartWare company. Does anyone have any suggestions?

[PaulH]

well for one thing, the db drivers are actually supplied by data direct. based
on that alone, i'd say these guys are probably clueless and would make me
suspect they have an issue and are looking at somebody to blame. you might ask
them if using data direct drivers instead would make a difference to see what
they say.

no idea what smartware is but do they have a JDBC driver? some more details
about it might help.

[jim-nih]

While the SmartWare vendor's tone may not be helpful, what he says matched what
some here are suspecting. The Remedy driver is not a full-functioning ODBC
driver as we understand it. It is a read-only driver. Is CF then shutting
down because not all the features are working with this driver? Since the same
Remedy driver works with version 5 for us with no problems, but fails with
version 7, it seems CF is being more strict or restrictive with drivers now.
In an email I received from [email]supportinfo@macromedia.com[/email] I was asked if there was
a specific query that caused this. No, it seems to be every query. The server
our MX7 is on also has no earlier version of MX on it that might pollute the
environment. (Replies to [email]supportinfo@macromedia.com[/email] are not possible as it
apparently trashes incoming mail, so I am replying in the forum.) We still
have the failure, and we have no clue how to fix it at this time.

[PaulH]

cf5 to cf6/7 was a complete change. the drivers that cf now uses depend on java
(some form of jdbc or jdbc bridge) and are supplied by datadirect. you might
poke around datadirect for your issues or look for jdbc drivers for these
databases.

[jim-nih]

Thanks Paul. I have now 'poked around' but found nothing helpful. I am still
stuck and getting desparate. Since Macromedia has chosen to use datadirect
drivers, would I get assistance from Macromedia if I purchased a Macromedia
support agreement? If not, do you have any other suggestions? It really
doesn't seem to me that the driver or CF is properly handling the interface to
the read-only Remedy driver.

[PaulH]

did you talk to anybody at data direct? did you see if there are any jdbc drivers for this thing?

i suppose you could open a support incident w/mm, if it's a bug you'll get your money back.