Precisely Speaking
February 04, 2012, 07:05:57 PM
Welcome,
Guest
. Please
login
or
register
.
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News
: So what's news with you? Tell us about it in "Getting To Know You"!
Home
Help
Calendar
Login
Register
Precisely Speaking
>
Training and Education
>
SB+ Programming Questions
>
Easy Question (I think)
Pages: [
1
]
Go Down
« previous
next »
Print
Author
Topic: Easy Question (I think) (Read 1056 times)
adewitt
Professional
Posts: 42
Easy Question (I think)
«
on:
April 20, 2010, 12:17:03 PM »
Epicor's Avanté
I am tasked with taking a workbench screen, hard coding all the options except one and presenting the one option as a single input screen. This calls a subscreen that is common both to this process and the original process. I have everything working except one thing.
I input my option, press F2 and the subscreen brings up the result. If I choose to ESC from the subscreen back to the calling screen the value is still on the screen. I don't want to add to the Proc After Esc on the subscreen because of its common usage so where can I put in on my calling screen so that it initializes the work variable but stays on the field?
I'm sure it can be done, but I can't for the life of me make it happen.
Thanks.
Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
Posts: 1524
Re: Easy Question (I think)
«
Reply #1 on:
April 20, 2010, 12:21:25 PM »
So when you escape from the subscreen you want the front screen to basically initialize it's values?
Logged
-Kevin
Accidents "happen"; success, however, is planned and executed.
adewitt
Professional
Posts: 42
Re: Easy Question (I think)
«
Reply #2 on:
April 20, 2010, 12:36:37 PM »
Only the value corresponding to the option on the screen. It's the only value that will change.
I tried doing it through a default value, but because it's one field if I pressed Enter before I pressed F2 I initialized the value when I didn't want to.
What the workbench does is allow you to build a list of things (in this case orders) to process. This is a new feature in the release we're upgrading to. The users whined that it was too much work that doesn't add value so I'm trying to simplify it while not ripping too many of the good things that I may need to use later. That is why I don't want to touch the subscreen if I can help it.
Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
Posts: 1524
Re: Easy Question (I think)
«
Reply #3 on:
April 20, 2010, 12:38:47 PM »
You shouldn't have to touch the subscreen. I assume this subscreen is being called via some subroutine or paragraph, right? If not, could you wrap a subroutine or paragraph around the subscreen? Then, after calling this process from the Process After Screen Accept, it would call the subscreen and then initialize your value and EXIT 1 to return to the calling screen.
Or am I oversimplifying the problem?
Logged
-Kevin
Accidents "happen"; success, however, is planned and executed.
adewitt
Professional
Posts: 42
Re: Easy Question (I think)
«
Reply #4 on:
April 20, 2010, 01:28:00 PM »
Yes, the subscreen is called within a paragraph. I tried putting my variable initialization statement here:
CALL SB.PROCESSS('SOPI9411.N')
CALL SB.CPROCESS('IIAFTER')
@WORK<11> = ''
@REFRESH = -2
EXIT
But my statements don't do anything if I press ESC in the subscreen.
Logged
Pages: [
1
]
Go Up
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
General Category
-----------------------------
=> Getting To Know You
=> Announcements
=> Big Thoughts / Cool Ideas
=> Rants & Raves
-----------------------------
Application Support
-----------------------------
=> Red Leaf
=> Activant/Prelude Support
=> Summit Support
=> Avante Support
=> PRC Support
-----------------------------
Training and Education
-----------------------------
=> Connect!
=> U2 Programming Questions
=> SB+ Programming Questions
=> Web Programming Questions
=> Business Intelligence / MITS
=> PC / Hardware / Miscellaneous Support
Loading...