Search results

For adding fields, I prefer a complete recompile, even if it is not immediately necessary. One example what might go wrong: define a temp-table like some database table pass this temp-table between two programs change one of there programs requiring you to compile it result: run-time error...

You could try Windows-1252. The 7F through 9F range in ISO8859-1 is either undefined or contains control characters. In Windows-1252 this range contains printable characters. 80 is the € sign. This is probably kind of a hack. The other answers would be preferable. The OpenEdge version shouldn't...

If the AppBuilder refuses to open a file you have no other choice than to at least modify the file with a different editor until the AppBuilder can open it again. Just take care what parts of the file you shouldn't modify: - Don't touch the &ANALYZE-Lines. - Don't modify generated procedures...

Thank you for the correction. We started using ROUTINE-LEVEL in our product with OE 11, BLOCK-LEVEL is planned AFAIR. (I don't write the statement myself, it is in our templates.)

As joey wrote, those includes are from oehive.org. With 10.2b you could use the built-in throw/catch/finally features. Some things to keep in mind: - Mixing the old (on error ...) and new error handling can yield strange or unexplainable results. - You can use routine-level on error undo, throw...

I don't know what you are trying to achieve exactly, but if you just want to display zeroes as blank fill-ins in the GUI you could set the field format to something like "zzzzzz". The stored value will still be zero/0.

Even Progress does it that way. Just look at the Downloadable Progress Knowledge Base (ProKB). That start menu entry runs a batch file which essentially calls _prokb.exe -ininame ProKB.ini -pf .\Startup.pf -p _ProKB.r (I assume _prokb.exe is a renamed prowin32.exe.)

My guess is that it is a 32-bit/64-bit issue. Assuming Windows Server 2008 is the 64-bit edition, cmd.exe is a 64-bit process and will see directory names as-is. If the Progress executable you are using is 32-bit (until recently prowin32.exe only existed as a 32-bit executable) it will see the...

If you rely on on-the-fly compile, you could just as well use compile time arguments. Much easier to read, and no temporary files. (I only use this for some special-purpose stuff where I have to go over all tables and which doesn't have to run in production.)

Indeed. If you run this in a production environment without source code you will get a runtime error (STOP error, probably) because program.p can't be compiled. One time such an error slipped by our QA. Apparently they also had source code in addition to .r-Code. And of course you have to keep...

I'm not totally getting what the OP is trying to achieve. I suppose it's not enough to write define variably xyVar like mytable.myfield no-undo. xyVar = mytable.myfield. ? Of course if you want to store the value into a temp-table or database table that won't work.

The label has to be placed directly in front of the statement which starts the block (eg. do:, for ...: or repeat: ) so it is just a matter of find the statement which ends the block, just like when there is no label. PDSOE also highlights the complementary statement when you place the cursor on...

CATCH only catches ERRORs, not STOPs. (Just verified this in the KB, also FINALLY is not executed after STOP.

Sounds good, and should definitely give better performance. Usually I would also include EndTime, but that will only help you if search for StartTime with equality ("=") which is not very likely. Now, if you did separate date and time into two fields an index on StartDate and EndDate would be...

I understand that each of these indexes only contains one column. A single index with all four fields will certainly work better, though in your example it will only use the first three fields since StartTime is compared with ">=" (see bracketing). This is definitely the way to do this properly...

Actually we do use quite a lot of inline includes, although that should get less because of the OOABL features. The main reasons for these includes are implementing optional parameters (which can be implemented in OOABL by overloading methods, but that still doesn't give you named parameters...

I think that term originates in the C language. Basically you have some preprocessor logic to prevent including the same include file more than once (eg. when it gets included from multiple library include files). We use this, too. It goes like this: xy.i has the following code: &IF...

Well, there is a MOUSE-SELECT-DBLCLICK event or alternatively a LEFT-MOUSE-DBLCLICK event. You could try to write something like ON LEFT-MOUSE-DBLCLICK OF wEdit : wEdit:SET-SELECTION(1,32000). END. (I didn't try it so it might work differently.)

I recently encountered this issue and asked Progress support about it. My example was slightly different: I had a unique primary index with four fields and another unique index with the same four fields in a different order. A find statement queried exactly those four fields with "=". The...

The answers are not quite correct. If you scan _Lock naively than yes, the time is related to the size of -L. But see the following knowledge base entries: http://knowledgebase.progress.com/articles/Article/P161995 http://knowledgebase.progress.com/articles/Article/000044741 You have to do the...