BattleBlazer 0 Newbie Poster

Hi

This post is more for information purposes rather than help. I have just been tasked to investigate the upgrade for our applications to run on Windows 7. Oh, yes - easy one might say... Not!!

We have a few applications running on a central Oracle server. To upgrade the code was easy, nothing really needed to change in the business logic. But one of the traps I was caught in was not testing the startup of our applications. For updates, an updater is first called to check for updates, which then starts the main application by using the Shell.Run command.

And here is where the funny is. If the application starts WITHOUT using the updater, it works and starts correctly. Although after this funny, I am not sure how stable the connection will be. If it starts WITH the updater, it either just exits (about 10% of the time), gives an error message about a DLL (about 20% of the time), refuses to connect to the database (about 30% of the time), or works properly.

None of us could actually believe that this was the Oracle Client. But once I changed the client to the new 11g Instant Client, everything works perfectly - apart from some Oracle Types - which is a separate issue.

So, just a warning, be aware of using the 10g XEClient on Windows 7.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.