Search results

You need to search for reducing a fraction. The following code adapted from some random JavaScript code found on the web (gcd = greatest common divisor): function gcd integer ( int, int ) forward. function reduceFraction returns logical ( x as int, y as int ): def var d as int...

Find <pct:compile> or the <PCTCompile> element in your build.xml and add it there (hint: it is on line 149 of db-build.xml). Since your build.xml is covered by version control, you will not lose the change accidentally. Adding it to startup.pf just means you need to remember to add it to all...

You need to add "-h 6" (or however many entries you need) as option.

Is Report Builder available in OpenEdge 10, 11 ? indicates that reports can only be edited with Progress 9, does that no longer apply?

Did you follow the steps at PASOE-How-to-add-a-new-SSL-certificate? What is GlobalSign.crt? Is it the GlobalSign Root R6?

Lucky you! Check the usual suspects: - Windows event viewer - install logs (with OpenEdge they are call oe*.log in c:\windows - no idea if they are created or what they are called when using 9.x) Things usually do not just disappear. The logs may help identify the problem, but not give a solution.

Progress 9.1B was released in 2000. That's 24 years ago, when Windows 98 and Windows 2000 were "cool", but Windows XP was still on the horizon, never mind Windows Vista, Windows 7, Windows 8, Windows 10 and Windows 11. The lowest version certified by Progress for Windows 11 was Progress...

Does not ring any bell. Since Progress have been calling REST transport a dead end for years, use WEB transport, I doubt that they will have invested in enhancements for REST transport.

Have you explored configuring PASOE / Spring to use the webauthn4j-spring-security extension?

It's been broken for a while - Help window resets when focus changed to code window

As an easy example use :1 - your code returns 0256 which seems to indicate that your high and low bytes are swapped. If you add: hexPart = substring( hexPart, 3, 2 ) + substring( hexpart, 1, 2 ). after the overlay you should be ok.

Hmm... it's a bit odd. ABL decimals are supposed to support 50 digits. If I just keep multiplying by two, the decimal behaves: def var i as int. def var de as decimal format '>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>.9' initial 1. repeat: display i de exp( 2, i )...

The problem is that ABL decimals are not accurate to 128 bits, try: message exp( 2, 127 ). If you want to go down this road you will need two 64 bit integers.

I generally just use google with a site filter to search progress.com: site:docs.progress.com output clipboard Output to the clipboard.

Start (pun intended) at pasoestart, and yes you are wrong about tcman being v12 related. Note that you can filter documentation on version.

The program you run from the command line cannot have any input parameters. -param will not pass input parameters, it will set session : parameter which you can use in a wrapper: run your.p ( entry( 1, session:parameter ), entry( 2, session:parameter ) ).

Are you deploying source code? We deploy 11.7, 12.2 and 12.8 r-code, so it would be: assign cSSLProtocols[1] = 'TLSv1.2':u &if proversion >= '12.8' &then cSSLProtocols[2] = 'TLSv1.3':u &endif But I do have my doubts about the protocol order, I would want 1.3 first if it can be...

So by restricting to TLS v1.2 you are not silently hanging on TLS v1.3 and now back into "normal" error territory - see Progress Customer Community

Check ciphers and transport protocols. These can be restricted by code or by environment variables - see Progress Customer Community There have been mismatches between what sslc supports and what the ABL socket supports. TLS 1.3 being an earlier troublemaker.

1. check your propath - are you referencing 11.7 libraries 2. message search( 'OpenEdge/Logging/LoggerBuilder.r' ).