I don't fully understand your question, but maybe this example can give you some ideas, (be sure you are not using -q parameter)
DEF VAR xtable-name AS CHAR NO-UNDO.
xtable-name = "table1".
OUTPUT TO temp.p.
PUT UNFORMATTED
"INPUT FROM table1.d." SKIP
" REPEAT:" SKIP
" CREATE " xtable-name...
DEF VAR i AS INTEGER NO-UNDO.
DEF VAR c AS CHAR NO-UNDO.
c = "your text".
DO i = 1 TO 15:
c = REPLACE(c," "," "). /* first "" with 2 spaces, second "" with 1 space */
END.
I suggest you to write the question to Forum - OpenEdge Development - Progress Community, it is common to receive responses from Progress staff and it seems only they know why is designed on this way.
With refresh option, on a "input type hidden" keep the "id" of the last field posicionated; and when the page is refreshed, use the javascript focus() to focus on the field.
With no refresh option, you could use jquery ajax, and call another webspeed program that update the database with the...
4.- With export you have an automatic break line, with put you must do an "skip".
5.- export take care if data contain delimiter character or quotes, with put you must take care of it
For #2 use the vanilla program that allow zero for rct-wo
For #1, as your program is custom, you can add validation for rct-wo and iss-wo was created, if not you can undo the transaction. How can you validate rct-wo and iss-wo?: ON WRITE OF tr_hist and validate both tr_type iss- and rct- was...
Works as designed.
If you select "Modify Backflush" you can modify the "Recepit Data Input" qty, and write Zero; this way only ISS-WO will happen and not the RCT-WO; btw, you can do the opposite too, RCT-WO happen and the ISS-WO no.
For revert you can do it on the same way.
Try only checking the last field:
FOR EACH < Table Name> Break by Col1 by Col2 by Col3 by Col4 by Col5 by Col6 by Col7 By Col8 by Col9:
IF First-of(Col9) THEN DO:
Initialize variables.
END.
Calculation part.
IF Last-of(Col9) THEN DO:
Printing the report row.
END.
Instead delete try to expire the BOM seting "End Date" value.
There are not direct impact if you delete the BOM, but for historical purposes is better to expire it.
Note: If you have custom reports, need to be sure all queries to BOM (ps_mstr table) are using ps_start and ps_end values correctly.
For the ^M yo can use something like this:
Converting Text Files for Use on DOS or AIX
Using sed, enter ^M on the command line by using the key sequence Ctrl-V followed by Ctrl-M.
sed 's/$/^M/' <filename> > <newfilename> UNIX -> DOS
sed 's/^M$/$/' <filename> > <newfilename> DOS...
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.