Search results

Any super procedure is a persistent procedure. In order for it to be a super procedure you can use the add-super-procedure method to add it to the session or a given procedure handle. With super procedures you are able to extend the functionality ( additional internal procedure or functions ) of...

Hi Rob, Thanks for you swift response. Apart from this issue I am so happy with the new RHEL System. Almost everything server-side is up to 6 times faster. I did check promon and I saw that all 24 servers were spawned - and most of them were exhausted with 15 pending connections. In the...

OpenEdge 11.7.3 on RHEL 7.5 (migrated from 11.3.3 Solaris last weekend). We are live with the new system and are facing a strange issue in that the users are getting the following error message: The server or the system has no more resources. Please contact Progress Technical Support. (748)...

The difference is weak (implicit) vs. strong (explicit) buffer scope. Without the "DO FOR customer" it is a weak scope and the compile extends the buffer scope to the outermost block which contains a reference to the buffer. In the first case it is the message statement referencing the customer...

You don't say anything about which version use - so one can only speculate. Nevertheless, you don't install the proxygen tool by itself - it comes with the installation of a development product. Which product it is depends on the version of Progress/OpenEdge you are using. In recent version of...

Probably there is no other reason than somebody designed it that way. Unless you have a sound business case - using find triggers is the road to hell. You will hammer the database and produce unnecessary network round trips.

Every SQL statement that is executed in the AVM is SQL89. Full Stop. It is not real SQL - it is some form of psydo SQL interpreted by the AVM.

The secret lies in standard block behavior which differ between a do - which does not have any scoping capabilities and and loops like repeat or for which do have scoping capabilities. Scoping capabilities - that is buffer or transaction scope. Understanding buffer and transaction scope is...

I think I found a solution: The default index does have an _Index-Field which actually points to an _Field with a blank name! OE11.7.3 that is. /* Inspect each index for the current table*/ for each _Index no-lock where _Index._File-Recid = recid ( _File ), first _Index-Field no-lock where...

Just in case: Does anybody know how to identify such an index which was created automatically due to the table not containing an index definition? I know their name is "default" - but I don't think using the name is sufficient as somebody could deliberately name an index that way.

Forgot to add, I am really mad and I am really inclined to pillory somebody. To me it is unacceptable that anybody can deliver schema changes without having to pass a review or quality toll gate.

I would love to. But, since I am not allowed to touch the production systems whatsoever and the time window for delivering the software package closes this Friday - I am hardly in the position to fix them now. But it is on m to-do list for beginning of next year. Me too. Database backup (...

Did anybody encounter tables without a single index yet in an OpenEdge database? By chance, only after the migration, I stumbled over 15 indexes which were residing in the schema area on the target system where they reside in the respective type II storage areas in the source system. Dammit -...

When you build a new window in the good ole AppBuilder it will generate a lot of code for you which will automatically work in almost all situations. The highlighted code does the trick ( enable_UI contains the code to view the window ) and the next statement makes sure that, when you run it...

That is when the buffer scope is larger than the transaction scope - at the end of the transaction scope an exclusive-lock will be downgraded to a share-lock. This is default behavior for as long as I can remember. Whether the default behavior is what you want is another story. Having...

Ooops :oops: - I think you got me

Unless you have a valid use case you should avoid a share-lock like hell. It might have been "okay" in the late 1980s of the last century where you had a max. of 1 user connecting to the database .... But, I have one valid use case: I have processes running against our database which must only...

Can't speak for OE12, but: In order to use a JDBC driver on a Windows system you need to install it. A copy of the *.jar files to the system is not sufficient. You need to install the SQL Client access from Progress on Windows. As far as I know it is a so-called deployment product which you can...

You find them in the Progress installation ${DLC}/java.

What do you mean by "free reference" and what is your point?