Search results

It's not as easy as just converting it. C# doesn't have direct access to the database, so you can't translate the logic at all. You're going to have to provide a lot more context.

I had a few issues with some programs. IIRC Outlook was a problem for a while. But yes, Eclipse was the worst.

They work fine in my experience so long as you set the High DPI Scaling Override correctly.

The number you're getting is the integer value of the handle. As Tom says, I would search the code base for other examples of where this is used and use that to work out what to do with the handle. You seem to be asking some very basic application specific questions here that we cannot help you...

Places to look for errors are: DB Log file Webspeed Broker Server Log Webspeed Broker Agent Log Any client logs enabled

Considering you can't do OO development in the AppBuilder, probably not.

I think your biggest limiting factor is going to be your Progress version. As @Osborne says there are other options, but you will be severely limited to be honest.

Thanks Rob - I've split it out into a new thread.

asbman etc are utilities for the classic AppServer and not for PASOE, hence why they aren't available. You will have already come across tcman when creating your instance. There is a utility called oeprop that you can use to edit the properties file, or you can do it with your text editor of choice.

I can't stress this strongly enough. DO NOT DO IT. PLEASE! This is not the correct process. It is deliberately opaque, convoluted and hard to maintain.

I definitely think structured error handling is the way to go. You would throw the errors from UI.p and catch them in main.p and handle them there. It might not be exactly what you want, but it's the essence of how structured error handling works.

I don't understand the question entirely, but if you're after a way of handling error, particularly unhandled ones nicely, then you want Structured Error Handling. This presentation is old, but gives a good starting point: https://pugchallenge.org/downloads2015/272_Strucutred_Error_Handling.pdf

Also, what OS is this?

Is this 32 bit of 64 bit? Are you absolutely sure of your version? It looks like this bug: Progress KB - Database experiences a forced shutdown with error 793 and 744

FWIW the code runs fine on 12.2.

Usually when a program crashes you get a protrace or a procore file which will give you more error detail. You may have to search around a but to find it though. Often it's in the start directory of the application, or possibly in the temp directory.

Nice! Not of interest to me, but I'm sure there are folks out there who might well want it for posterity.

You may be better served to start your own thread, linking this one. Starting a new conversation on a thread that is 19 years old is unlikely to bear much fruit.

Following is a newsletter from White Star Software, Consultingwerk and Riverside Software: You may have heard that there is a critical security vulnerability in the “log4j” Java library that is used by many applications in the Java ecosystem and you might be wondering if this impacts your...

Do you have a specific problem? At the moment this just seems to be a statement.