Search results

You may start by reading about the 'output to printer' command and the -o startup parameter in the progress help.

To do that you need to access it through an OCX. Try any of these links http://www.google.be/search?hl=nl&source=hp&q=outlook+calendar+ocx+control&btnG=Google+zoeken&meta=&aq=f&oq=

Where are you running from ? from oe architect ? from a shortcut on your desktop ?

I have asked a question about this on the Exchange 2009. Try-catch cannot be used on stop conditions. Apparently this is exception handling and not error handling.

Fact is that when you have procedures that are run persistently and stay in memory for a long time, release makes a lot of sense. I have solved many bugs with adding an explicit release statement anyway. :awink:

As long as progress knows how to convert the database codepage into the internal codepage you should be fine. Check the prolang/convmap folder in your openedge installation to see which codepages are installed. What problem are you having ?

Strange that proutil has a IDXACTIVATE qualifier, but not a IDXDEACTIVATE qualifier. :confused:

Or you could use rcode-info. rcode-info:file-name = "...r". MESSAGE rcode-info:table-list VIEW-AS ALERT-BOX INFO BUTTONS OK. This will give you database names AND table names, but it is still better to have too much info than not enough. :awink:

LOL I can still remember very old development guidelines saying you MUST use can-do before lookup because it was faster.

What do error-status:get-message(1) error-status:get-message(2) error-status:get-message(3) ... return ?

As I understand it, the compile statement can only be used to compile a single file, not an entire folder. You can use 'run _comp.p.' to run the application compiler but this will only start the tool and not compile anything. Is there a way to pass parameters to the application compiler and make...

Yet, run value is not always a sign of bastard, cobbled, hamstrung OO ;). You will always have exceptions. Take for example a report daemon where one of the parameters of incoming requests is the report name. What else can this daemon do but use run value to run the report ?

looks like a simple typo :confused:

isn't it written in C++ ?

inoutTime = now should be all you need. (inoutTime is of datatype datetime or datetime-tz I presume ?)

This is from the documentation on the 'export' statement : A Format phrase with an EXPORT statement is ignored. Maybe you should use the 'put' statement in stead of the 'export' statement.

You cannot connect and access a database in the same .p. You need 2 programs.

not if you use the int64 data type :awink:

DEFINE VARIABLE hCPL AS HANDLE NO-UNDO. create client-principal hCPL. When compiling this code on unix and running on windows, you will get error (4438) Program was compiled under another incompatible display environment. Cannot run without recompile. Is there any way to avoid this...

This might help : in stead of directly connecting to the database, first make a socket connection to check the availability. DEFINE VARIABLE sk AS HANDLE NO-UNDO. create socket sk. sk:connect(" -S " + "ta1-arch1" + " -H " + "hostname") no-error. if not sk:connected() then ... This...