Re: Oracle Client Conflicts
Date: Sun, 29 Oct 2000 18:03:28 GMT
Message-ID: <QDZK5.13292$NP.985597_at_news.flash.net>
> The Dev/2000 application uses the V2 triggers from 10 years ago. This
feature
> is supposedly no longer supported. If this app had been modernized, we
could
> remove the 7.3.3 client altogether and run it on the Forms 6.0 runtime in
the
> same home with the 8.1.5 version of OO4O and the 8.1.5 client.
We almost got burned with that same problem. I guess you're talking about a massive conversion effort then with getting rid of the V2 triggers, huh?
> I guess the question is: If you can get the dual homes business working,
does
> it work reliably when the users runs applications from both homes at the
same
> time.
I'm not sure you can pull this off. I think you'd have to run one, then the other, or setup a batch file that resets the environment under each session. IE. Depending on what version (4.5 or 6i), that versions' stuff, usually in \orant\bin, must appear first in the search path. I think this is all the home switching does, other than maybe tweak a registry key that says the default home is home0 vs. home1.
> The Language Group support people said "Home switching" is done by a
> separate application they provide, and that it wouldn't be safe to use
both
> homes simultaneously.
I'm running 2 versions of applications right now and I've never noted a problem. I have the 4.5 developer tools and runtimes (from Developer 1.3.2 32-bit) in d:\orant, and the 6i stuff in d:\ora6idev. I don't run anything to tweak the homes and can run applications created with either version. We are, however, in the process of migrating the 4.5 application to 6i - unfortunately, it's 120+ forms and 50 reports. We have 2 developers, myself included, and we do the networking, dba duties and handle user-support calls as well, not to mention fixing all the bugs and adding enhancements. Oh the fun!!
Good luck. Received on Sun Oct 29 2000 - 19:03:28 CET