We have written some progress e-mail functions based on mutt if you are interested. You would need to install mutt of course. We even have a character UI.
Well, unless the users are accessing some sort of share, where they have centralized access to one single body of r-code, it HAS to be installed on the client machine. But in either case, that's not the where performance hit is. The problem is the data. The client is maintaining a live...
Let's do a terminology sanity check:
Server: The machine where the DB lives. Also know as "host"
Broker: A Progress process running on the host or server that allows clients to access the DB
Client: A Progress session (which can run on the host OR on a remote machine), that, through the...
There are no major differences in making remote connections between v9/v10 Progress and V6. All of the documentation for V9 is online at the Progress Website, but basically you need to:
- add an entry to your /etc/services file for each database you want to connect to . Simply create a...
Actually, you have at least 3 options:
1) Use the include file approach (.. groan )
2) Use the MAP-TO option when defining functions (booo ...)
3) Use a SUPER PROCEDURE!!! (crowd roars it's approval) :)
In Windows, I found no way to eliminate the window completely. At the very least it will be minimized. I remember dealing with tech support on that. I guess that's why they call it Windows? :-)
"The record will be unlocked as soon as the transaction is done. Any errors in the write trigger requiring an undo will only be handled correctly if the release is done within the transaction block (weak transaction)".
Incorrect.
There is no such thing as a "weak transaction".
There is...
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.