Search results

Look at the RUN xx ON server ASYNCHRONOUS EVENT-PROCEDURE "callbackproc1" . Statement. This will call your app server method and continue running your other statement after. Once the appserver response comes in it will call the procedure "callbackproc1" . You can find more info on this...

Here is some code i created to generate a .sql file to grant SELECT permission to all your tables in your database. Just replace the initial value of cUsrName to the user you want to give permissions to. DEF VAR cLigne AS CHAR. DEF VAR cUsrName AS CHAR INIT "test". OUTPUT TO odbc.sql. for...

There is no way of avoiding the slowdown that populating your SystemTracker table will create. You can get some performance back by using a query that only brings back the user-ID from systemTracker table but it will be marginale compared to what you will experience once the SystemTracker...

Here you go , it works in Version 10 tho. ASSIGN fld1 = "pt_domain" fld2 = "pt_desc1" fld3 = "pt_um" for each pt_mstr: display BUFFER pt_mstr:BUFFER-FIELD(fld1):BUFFER-VALUE BUFFER pt_mstr:BUFFER-FIELD(fld2):BUFFER-VALUE BUFFER...

Between version 9.0b and 10.1B the .WRX generated by OCX has been changed to support Unicode. What this means is that any WRX generated by 9.1E or higher will not be compatible with version 9.0B . This is the only known problem that you can encounter with VPE while working in 10.1B ... So...

Could you be a little more specific please? What kind of tests do you want to run? What exactly are you looking to test? Are you looking for a profiler or a debugger ? Do you want to test your execution speed , do you want to test if you have errors in your code ? Do you want to do Unit...

wow very nice code, Thanks alot Casper,

Hello everyone, I saw many messages about using Webspeed and pdfinclude for reporting . But i have a question beyond generating the report itself. pdfincludes generates a pdf file on your system but what technique do you use to get that file to the Webstream. I see 2 ways that it can...

Codejock has some really nice ActiveX in the Suite . You have everything to give your progress App a Office 2007 look. I am pretty sure they're is a trial version available.

.Net in Progress will be very useful for business like us who have a huge UI already in progress and can't rewrite it in a single stroke . It will permit us to rewrite part of it and use .Net controls for new windows without our clients having to buy a AppServer or have 2 Clients (one in...

def var x as char. x = 'abc445098'. IF INDEX(x,'445') > 0 THEN MESSAGE "445 was found".

DEF VAR cStr AS CHAR INIT " 6/15/04~1~12934~1235322~err". DEF VAR cRes AS CHAR. cRes = ENTRY(3,cStr,'~').

But keep in mind that even if you change the ini file during a session , it will not change your current session since the ini file is loaded at the start of the client.

bah stupid bot reviving old posts :mad:

Hi , you can find all the information about setting up webspeed and how it works in this progress online document. http://www.psdn.com/library/entry.jspa?externalID=1908&categoryID=460

I found that the best way to add objects online is to load a .DF of the change thru the data administration with the add on-line option checked. That way you make sure that your schema lock is minimal compared to running the dictionnary with the option that permit you to create fields online.

Running a procedure Persistent does not make it Multi-Threading . Your program will still wait for your code to finish.

It time like these you wish Progress had try and catch hehe. but if you want to run your program in batch without any output to screen just do a OUTPUT TO xx.log. at the start of your program . It will send all your screen output to the file. ex: OUTPUT TO yourlog.log. RUN YourProc.p...

Here a procedure that will calculate the time difference between 2 INPUT time in HH:MM:SS format and send it back in HH:MM:SS format. PROCEDURE CalcTimeDiff : DEF INPUT PARAMETER pcStartTime AS CHAR. /* HH:MM:SS format */ DEF INPUT PARAMETER pcEndTime AS CHAR. /* HH:MM:SS format...

DEF VAR iStart AS INT. DEF VAR iEnd AS INT. iStart = TIME. RUN Proc. iEnd = TIME. MESSAGE STRING(iEnd - iStart, "HH:MM:SS"). You can also use ETIME if your progress version supports it. ETIME(true). RUN Proc. iElapse = ETIME. MESSAGE STRING(iElapse, "HH:MM:SS").