Search results

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.

You need some sort of license for the database on the second machine. A DR license is what you need to do that. It will be cheaper than a full license.

The trigger code needs updating then to better handle the record not being lockable. And then you need to find the code that is locking the record for too long and fix that too.

I would be very surprised if that's a working database. 4GB backup, 8MB data, 1.6GB of BI looks weird. But the "odbk" probably stands for OpenEdge Database Backup and is therefore probably where I would start looking. The good news is that Sage Intergy still looks like it has an active website...

Even without the output your process is completely wrong. It should be something along the lines of the following: Enable AI on the source (and enable the ai archiver too probably) Configure the sports2000.repl.properties files for both source and target. Enable the source DB for Replication...

I stand corrected. I thought it was an Enterprise feature.

First of all, Auditing requires a license. It may be it's already included in your license, but a license is required for the tool nonetheless. That being said, and IMHO, you are approaching this all wrong. Not all data replication are created equal. You first need to evaluate what you want to...

I've no idea if it's the most efficient, in fact it almost certainly isn't, but it definitely plays to my geeky side... https://abldojo.services.progress.com/?shareId=619bbe4ac552423dc846eb6a Can't beat a bit of recursion on a Monday morning.

Have you tried a Knowledgebase search? This one looks relevant: Progress KB - Error 9908 9909 trying connect to AdminServer on UNIX.

_proapsv is an appserver process.

Definitely heading the right way. As Patrice said, the chances of there being an update elsewhere are very slim but if you have to account for it then you're ok. One note though - FIND FIRST should almost never be used. If there really are multiple records that satisfy the FIND then you want...