Power Builder + PL Developer

[jortiz]

Hello,

when I execute a power builder application, It doesn't open until I close all plsql developer windows. Just when I close plsql developer window, power builder program starts running.

Does PLSQL DEVELOPER have any bug related with this?, do you how to solve the problem ?

Thanks !!

 

[jasonvogel]

It's not a PowerBuilder...PL/SQL Developer issue technically. You would see this behavior if were opening something else that whose startup is "big". PL/SQL Dev is gready about how it starts up from a splash screen standpoint. It holds the WindowOnTop process...PB's startup tries to do something similar...but it should still be starting. I run PB6.5.1, PB 7.x, and PB 9.0.1 without issue. But, I agree that PL/SQL Dev shouldn't be as greedy about its startup.

Jason

 

[Marco Kalter]

We have had some additional reports about blocking other applications. We have not been able to reproduce this, but the upcoming 6.0.2 may fix it anyway.

Note that you can suppress the splash screen by supplying the NOSPLASH command-line parameter. For example:

"C:\Program files\PLSQL Developer\plsqldev.exe" nosplash

 

[jortiz]

So what to do ? Isn't It possible to work with both at the same time ??

 

[jortiz]

Well Marco Kalter, Thats right, !!! I got It solved !!!

 

[jortiz]

I was testing the solution yesterday and I found the problem again, not as common as 3 days ago, but I still have It with some power builder applications.

 

[Marco Kalter]

Can you download the current 6.0.2 and verify if this helps?

 

[jortiz]

I've installed plsql developer 6.0.2 and I still have the problem here in my company. and all round automations said in the txt of this release:

* Fixed a problem starting specific applications when PL/SQL Developer
is running

Are they talking about my problem ??

I'm still looking for a solution !!!!!

 

[Frans]

Had the same problem with a number of applications: when PLSql developer is running, it will prevent some other applications (i.e. pythonwin, word97) from starting completely.

I discovered that changing the preferences for 'Check online updates interval' and 'Check online news interval' to the default to 'Never' solves the problem. (The check would because of missing proxy settings)

 

[Marco Kalter]

This should no longer be necessary in the current release though.