Progresss 9 and 10 ODBC driver to coexist

[th0]

Hi all,

Just a quick query, I was wondering if the ODBC drivers for Progress v9 and Progress 10 can coexist?

What I've done, is installed Progress client (PROGRESS 9.1D Shared Network Installation) on the desktop. This is working all fine, until I installed Progress v10 client.

After the Progress 10 client installation, the v9 odbc connection no longer works. However, there are no indications of a connection errors, as there are not error messages connecting from MS ACCESS.

The good thing is, Progress 10 client works magically!

Are there any concrete facts that Progress 9 & 10 ODBC client can't coexist?

Thanks

th0

 

[vdennis]

The drivers are indeed different. You must use the version 9 drivers for v9, and version 10 for OpenEdge. I can't recall if OE10 will connect to a V9 db, but if it will only the machine running the CR reports would need to be running V9. ALSO, the runtime ocx that comes with Progress 9 for CR9 will not work with OE10. And to top things off, you cannot just copy the needed files if you are using the RDC. These must be 'installed' using a program like InstallShield.
-Dennis-

 

[itman]

Hi.

My experience suggests 9.1d driver and 10.0b drivers work together ok on the same pc. However, with Crystal, you have to quit Crystal after using one driver (ODBC connection), in order to use the other. With Crystal Enterprise you have a problem whereby it can only maintain a connection using 1 driver at a time. You have to restart one of the Crystal services (page server, or cache server or something) in order to use the other driver - thats not a solution though.

I just had to build 2 separate Crystal Enterprise portals to solve this - a real pain.

As for .NET, well you can use the ReleaseObjectPool procedure to close off the connection after each request. Works well with my web services to both a 9.1d and a 10.0b database.

Hope that helps. I would love to get Crystal Enterprise working with both drivers on the same installation though.