Ben: I understand your problem. I think I would try getting the choice on either a combo-box or a field menu within the form, not an eep. It sounds like the eep will always replace all rows displayed. And, there are situations where only the choose command in an eep will provide the menu you want.
Jim Blackburn Ben Petersen wrote: > > Jim: > > > You should be able to set a variable in the Form Variables section to get the >information you need. Then display the variable. I have done that successfully in a >tiered region. The same will work in the header. This would have one field for the >selection and another to display the variable. > > I may have done something wrong, but when I tried a variable in the > region the same value was displayed on all lines if a recalc var was > executed, or if the user does something that causes the var to be > re-evaluated. Couldn't find a way to make it acceptable. > > > If you want to have one field, select the account # and display the account# but >return the linking number, I think the multi-column menu on a drop down box will do >that. > > I'm using choose, displaying the account name, and returning the > linking number, which looks and feels pretty good. It's the above > that's got me. > > Thanks! > > Ben Petersen > > > Jim Blackburn > > Kodiak > > > > Ben Petersen wrote: > > > > > > Hi All, > > > > > > I was wondering how others are doing this, or similar. > > > > > > I have an invoicing form with the typical header info for the first > > > table, detail lines in a region as the second table. For this project, I > > > didn't want to input the actual GL account#s, but a > > > reference/linking ID# to the GL, which allows changing account > > > numbers w/o updating invoices (and everything else). > > > > > > I use an eep to choose the the the account# and it updates the > > > invoice based on a autonumber column... but how does a person > > > actually display the account# rather than the linking ID number? At > > > this point I'm using an eep to display info in a single variable as the > > > user [F8]/[F7]s their way through the region. But better if the > > > Acct#s could display on each line. > > > > > > tia, > > > > > > Ben Petersen > > > ================================================ > > > TO SEE MESSAGE POSTING GUIDELINES: > > > Send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: INTRO rbase-l > > > ================================================ > > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
