Thanks, Ben.  Good point.
Jim

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Ben Petersen
> Sent: Friday, August 24, 2001 1:34 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Pop-Up Display Not Current
> 
> 
> Jim,
> 
> Deleting where count = last could delete an entry made by another 
> user in a mu environment, better count = insert.  Or, better yet, use 
> parameters that would get rid of incomplete rows in general... ie 
> "where item fails" or "where item fails and price fails", whatever 
> makes sense. Then you won't have to worry about how to skip the 
> command and can clean up user left-overs also.
> 
> Ben Petersen
> 
> 
> 
> On 24 Aug 2001, at 8:06, J. Andrus wrote:
> 
> > Mike, Ben, & Jim
> >     Mike's SAVEROW suggestion seems to have solved the problem 
> but with one
> > glitch, which although resolved, I don't quite understand.
> >     After leaving the ORDER ENTRY form to add a new customer 
> using the CUSTOMER
> > ENTRY form, the SAVEROW command is done in a CUSTOMER ENTRY 
> form EEP after
> > all customer data has been entered into that form.  Control 
> then returns to
> > the ORDER ENTRY form where the option exists on another field 
> to add a new
> > contact person for the new customer just added.  If yes, the 
> CONTACT ENTRY
> > form is entered from the ORDER ENTRY form, and the newly added 
> customer now
> > shows on the pop-up as I wanted it to so it can be associated 
> with the new
> > contact person.  The new contact can then be entered, control 
> returns to the
> > ORDER ENTRY form which can then be completed.  When it is all 
> over and done
> > with, there is a new order, a new customer, and a new contact 
> in each of the
> > respective tables.
> >     The glitch is that an extra row is also generated in the 
> ORDER ENTRY table
> > reflecting the status of the data present in that form at the 
> time the new
> > row was generated for the customer table by the SAVEROW command in the
> > CUSTOMER ENTRY form.
> >     Although I don't understand why that useless, and incorrect, row is
> > generated in the order table by the SAVEROW for the customer 
> table, I can
> > solve the problem by doing a DELETE ROWS FROM tord WHERE COUNT 
> = LAST in an
> > EEP prior to the final exit from the ORDER ENTRY form.  Now all 
> I have to do
> > is bypass that DELETE ROWS command when a new customer is not 
> added as a new
> > order is being entered.
> > 
> >     Thanks for the help and suggestions.
> > 
> > Jim
> > 
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]]On
> > > Behalf Of Ben Petersen
> > > Sent: Thursday, August 23, 2001 11:23 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: Pop-Up Display Not Current
> > >
> > >
> > > Jim,
> > >
> > > I'd have to agree with Mike. Seems like the record isn't being
> > > saved... but you _should_ get a prompt to discard or save. You
> > > might double check your pop-up parameters, failing that, try
> > > substituting a choose for the pop-up.
> > >
> > > One other idea.  I recently wrote a PO system where the Vendor
> > > record looked like a PO. We called it a template. All the standard
> > > PO header info _is_ the vendor record, and the detail region is used
> > > to generate a the actual PO  (there is a 'Make PO' button).
> > >
> > > When an order is going to be placed the operator selects the
> > > Vendor from a choose.  The record presented to him is a duplicate
> > > of the last PO to the Vendor.  Most often he clicks 'Make PO' w/o
> > > doing anything else. The eep calculates the next PO# /Date and
> > > inserts the required info into the PO tables. It's also handy if
> > > something has changed regarding the Vendor or PO terms since
> > > he doesn't need to goto a separate form.
> > >
> > > I've thought the same thing would be handy in some order entry
> > > systems where the orders tend to be repetitious, or the customer
> > > often wants to know what they ordered "last time".
> > >
> > > Ben Petersen
> > >
> > >
> > >
> > >
> > > On 23 Aug 2001, at 13:29, J. Andrus wrote:
> > >
> > > >         In my ORDER ENTRY form I have an EEP that exits to a
> > > CUSTOMER ENTRY form
> > > > when necessary to add a new customer and then return to the
> > > ORDER ENTRY form
> > > > to proceed with entering additional order data..
> > > >         Then, in the Contact field  of the same ORDER ENTRY form I
> > > have another EEP
> > > > that exits to a CONTACT ENTRY  form, if necessary, to add a 
> new contact
> > > > person and then return to the ORDER ENTRY form to continue 
> with entering
> > > > order data
> > > >         In the CONTACT ENTRY form there is a pop-up that displays
> > > all customers so
> > > > the appropriate customer can be selected to associate with the
> > > new contact
> > > > person being added.  However, the new customer just added 
> above does not
> > > > display in the pop-up.
> > > >         How can I get the customer just added above to show in the
> > > CONTACT ENTRY
> > > > form pop-up?
> > > >
> > > > TIA
> > > > Jim
> > > >
> > > >
> > >
> > >
> > 
> > 
> 
> 

Reply via email to