OE 10.1C table update help needed

davidbeberman

New Member
Hi all,
I am relatively new to Progress 4GL programming and have been given the task of helping to cleanse data tables in preparation for a upgrade.

The environment is Openedge 10.1C.

The .p file I have written contains:
/*PROCEDURE DGB_OrderHead_Upd_SalesRep :*/
output to e:\OrderHed_082609.txt.
DEFINE FRAME frm-orderhed
orderhed.company
orderhed.ordernum
orderhed.orderdate
orderhed.salesreplist FORMAT "X(10)"
orderhed.character10 FORMAT "X(20)"
WITH TITLE "Daves Test" USE-TEXT.
on write of orderhed override do:
end.
for each orderhed WHERE SalesRepList CONTAINS "ALEX|ALEXP|DEBBIE1|DEBBIEA|JIMP|JIMP 1|JOHNB|JOHNB 1|KENDRA|KENDRA1|KIMBERLY|MIKEO|MIKEO 1|d J|ELLIE|FOSTER|FREDG|JENI|MARILYN|MAUREEN|MIKEB|WORTH" with FRAME frm-orderhed:
assign orderhed.character10 = "INACTIVE".
display company ordernum orderdate salesreplist character10.
end.
output close.
/*END PROCEDURE.*/

The output from the seemingly simple update is:
Daves Test
Company----- -------Order-Order Date- Sales Reps---- C10-------------
FERGUSON 1609 12/11/96 ALEXP INACTIVE
** "db/repl/orderhed/write.p" was not found. (293)

The database does not update the character(C10) field to "inactive".
The table database triggers do not exist - ive checked the data dictionary how would I procede to sleuth down how to move forward?

Any help/advice is appreciated.
Thanks,

Dave
 
Hi all,
I am relatively new to Progress 4GL programming and have been given the task of helping to cleanse data tables in preparation for a upgrade.

The environment is Openedge 10.1C.

Huzzah! A modern, up to date and supported release!

CODE tags make code much more readable ;)

The .p file I have written contains:
Code:
/*PROCEDURE DGB_OrderHead_Upd_SalesRep :*/ 
output to e:\OrderHed_082609.txt.
DEFINE FRAME frm-orderhed
orderhed.company
orderhed.ordernum
orderhed.orderdate
orderhed.salesreplist FORMAT "X(10)"
orderhed.character10 FORMAT "X(20)"
WITH TITLE "Daves Test" USE-TEXT.
on write of orderhed override do:
end.
for each orderhed WHERE SalesRepList CONTAINS "ALEX|ALEXP|DEBBIE1|DEBBIEA|JIMP|JIMP 1|JOHNB|JOHNB 1|KENDRA|KENDRA1|KIMBERLY|MIKEO|MIKEO 1|d J|ELLIE|FOSTER|FREDG|JENI|MARILYN|MAUREEN|MIKEB|WORTH" with FRAME frm-orderhed:
assign orderhed.character10 = "INACTIVE".
display company ordernum orderdate salesreplist character10.
end.
output close.
/*END PROCEDURE.*/

The output from the seemingly simple update is:
Code:
Daves Test
Company----- -------Order-Order Date- Sales Reps---- C10-------------
FERGUSON 1609 12/11/96 ALEXP INACTIVE
** "db/repl/orderhed/write.p" was not found. (293)

The database does not update the character(C10) field to "inactive".
The table database triggers do not exist - ive checked the data dictionary.
how would I procede to sleuth down how to move forward?

Well something thinks the trigger exists...

You might try creating an empty trigger procedure in "db/repl/orderhed/write.p".
 
Thanks for advice on code tags - will use them in the future.

The directory structure db\trg\... does not exist on the server BUT a little more sleuthing shows on the original database (progress 9.1D) the structure does exist.

The conversion was bringing the data of the application Vantage 5.1 up to Epicor 9.

I have to assume that during the data conversion done to bring the data up about 6 revisions (and 5+ years), that some setting still points back to the original directory structure.

Where would I look for the settings file(s)?
 
Tom,
Thank you for the help to this point.
Running a trigger report from DD shows all listed tables having triggers pointing to the old structure.
Open question is whether the application Epicor 9 needs these triggers(brought forward from the old applications version) or is it alright to simply delete all trigger references.
But I believe that may be a question for the Epicor folks - would you concur?
I'm so new at Progress (but 25 yrs in coding) that I couldnt tell if it was something simple I had missed.
Thanks again,
Dave
 
If all you are doing is upgrading from some old version of Progress and running the same code base then, yes, they would still be needed.

If you are doing something that involves code updates from Epicor then you would have to ask Epicor.
 
Back
Top