Search results

I think the problem is the COM Object. If your program asSendRedemptionEmail.p only send email, then you could consider using something like smtpmail.p http://www.freeframework.com/downloads/new/smtpmail/

I've never tried this before, but it seems that you have to set the Frame attribute on the Field-Level Widget to your frame handle. If I use your example: (first) ASSIGN bpsave:FRAME = hFrame. (Before) ASSIGN bpsave:SENSITIVE = .... (and do not use "IN FRAME hFrame" because you cannot use the...

I may be wrong, but can't you just define a second buffer for the temp-table, then you can use the same temp-table but just with a different name? As Casper pointed out, it all depends on what you would like to do with the "copy" of the temp-table. Willie

DEFINE VARIABLE newhandle AS HANDLE. /* Add to your code */ ... Rest of main procedure ... /* Sub-Procedures */ PROCEDURE xxxxx: DEFINE VARIABLE chCtrlFrame AS HANDLE. chCtrlFrame = .... ..... the rest of your code here just before you call sub-procedure viewreport...

In some circumstances I also found that a handle is no longer valid in a sub-procedure. What I did was to define another handle in the main procedure and to assign the new handle equal to the handle I need before I call the sub-procedure. In the sub-procedure you need to replace the handle...

The best strategy would be to avoid errors rather than to catch them. In your sample code I would replace the 11 with EXTENT(v-array), in this way you can never exceed the array bound. Your error.p would then look like this: /* error.p */ DEFINE VARIABLE v-array AS INTEGER EXTENT 10. DEFINE...

I don't know the detail how, but have you ever considered using COM objects that can be accessed directly from Progress ABL/4GL. If it can work on MS Outlook & MS Excell then surely it can work for MS Access.

Unfortunately we still running Character client from a Unix server, so all the nice goodies from Microsoft is still out of reach, hopefully not for too long. In the meantime it seems like buttons is the best alternative.

We use the following code for a strip menu on some table maintenance programs: DEF VAR vcmenu AS CHAR EXTENT 11 FORMAT "x(11)" INITIAL ["Create","Modify","Delete","First","Last","Next","Prev","Key","Exit"] NO-UNDO. ... DISPLAY vcmenu WITH FRAME menu CENTERED NO-LABELS ROW 18 NO-BOX...

I'm not sure what the problem is, but I use a simple PDF template and then add my images to it with: RUN pdf_load_image("Sord","Logo","logo.jpg"). RUN pdf_place_image("Sord","Logo",50,100,60,80). This is placing my 60X80 pixel logo in the top lefthand corner. You can play around with the size...

I cannot find something at the moment to launch the Outlook Address book and I don't know if it exist because it is part of MS Outlook. What I found that work for me with COM objects is to go to the Visual Basic Editor in the MS application. In Outlook go "Tools", "Macro", "Visual Basic...

I avoid using: "For each ....., each ....., each..." it is very slow and you could get duplicate data, when some of your data is not as it is supposed to be. But you lose your abillity to sort on different fields in different tables if you don't use it. What I suggest you do is to...

What about importing the csv file and then use com objects to create the contacts in outlook. The following example code will create a contact in outlook. I'm using MS Office 2000, but I'm sure it will work on 2003. def var hout as com-handle. def var hitem as com-handle. create...

A transaction is one iteration of the outermost FOR, REPEAT or procedure block that contains direct updates to the database (INSERT, CREATE, UPDATE, SET, ASSIGN or DELETE of any database record). Other transaction blocks that you get are: 1. Any block statement followed by the TRANSACTION...

Hi, I would say no it will not effect the order of the break. Your example should work fine, but be careful if you use IF FIRST(....) & IF LAST(....), because the record after the NEXT statement could in some instances not be the FIRST / LAST record. If you use FIRST(...) / LAST(...) statements...

Rene, Keep your transaction block to update the control table as short as possible, and keep the updates to the database and the FIND EXCLUSIVE-LOCKS in a seperate transaction block, so that your procedure doesn't become a transaction block. I do something simular with automatic order numbers...

Rene, "release control" will only downgrade your exclusive-lock to a share-lock, so the next user cannot get an exclusive-lock on "control". You can either omit the exclusive-lock, or start a transaction block by changing: "if not avail order then do:" to "if not avail order then do ON ERROR...