Say I wanted to load some data into a database table and I knew the procedure was in single-user mode, is it possible to programmatically disable an index? And then rebuild it?
It sounds as though your ABL code is performing the actions of a client, not server, therefore your methods would probably simply send a command, then read the response. The WRITE and READ functions are blocking (which means the processing will pause until either the buffer is full or the...
While I'm here, here's a code sample for checking if the current version of Progress is high enough (where {1} is the required version):
if (if index(proversion, ".") eq 2 then "0" else "") + proversion lt "{1}" then
do:
message "Cannot execute: Progress OpenEdge {1} or higher is required."...
Anyone know how to retrieve the Progress/OpenEdge version number? I was hoping to find a pre-processor name, but the best option I can find is parsing the 'version' file in the DLC directory.
I seem to recall there might be some undocumented pre-processor names.
Ahh I think I have the answer already: I'm running 10.1B on Linux and 10.1C on Windows; apparently there's a bug in 10.1A-B (Bug# OE00151650) which causes this.
(see P124156)
I am having a problem with a wait-for with a sole condition of U1 of the current procedure. The wait-for statement is below, and works fine in batch mode on Windows, but not Linux.
wait-for U1 of this-procedure
pause vl_pause. There is one procedure defined in this program which has the...
Thanks for the suggestions guys.
I might see what I can achieve with SESSION:FIRST-BUFFER; but I think the best way to go will just be adhering to the PEG rules...
I'm in a situation where I need to get references to all temp-tables and/or workfiles in a procedure so I can empty them.
Of course being the good programmer I am, I should always clean them up in my code.. but no-one's perfect. I was hoping to create a utility function to loop through all...
I don't know the situation, but is it possible that input blocking statements are not necessary for your socket communication? Maybe you could get away without using them.
Otherwise maybe you could move the socket logic to a separate .p file and run the .p file.
As Progress does not support foreign keys, it's typically a hard job extracting relational data -- because there is none!
See this discussion at the OpenEdge Hive: http://www.oehive.org/node/1161
If you'd like the script mentioned in my post just let me know.
Sounds like your Procedure Editor session is not connected to a database.
To connect to the database, either create a shortcut to Progress with the relevant database connection parameters (-db) or click Tools>Data Administration then Database>Connect and use the following dialog box.
From here...
Or a less standard solution: you could use a server-side script to run a Progress client and execute your script. For example:
shell('$DLC/bin/_progres -b -db mydb -p mypfile.p');
To capture the output.. hrmm only thing I can think of right now is using a temp file.
And this has the obvious...
As far as I'm aware, there's no function to dynamically evaluate a string as code (like the eval function in some other languages). And I can't imagine any other way to do this sorry..
There are probably a few ways to do this. Depending on the situation, I'd probably recommend creating both windows from the same procedure (.p). Then you can easily assign/display from a local variable.
Also you should be able to easily close the other window. In the trigger, just call "delete...
Careful though!
STRING(ar_date) will produce a string depending on your locale setting which probably won't sort very well.
For sorting as a string, you'd want your date in a format like YYYY-MM-DD, which can easily be achieved with ISO-DATE(ar_date)
Good point, however in this case if the stream is closed, it's closed for a reason. Oh well it probably makes sense now that the reason gets a variable named after it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.