Re: Limit Data Input
- From: "Ron2006" <ronnemec@xxxxxxxxxxx>
- Date: 2 Feb 2007 05:39:09 -0800
The subforms are bound in a parent child relationship.
The SO# is entered at the time a job is entered so it is neccessary to show
it on the form. The form has several tabs and includes a tab for invoices to
be entered and a tab for payments to be entered. When an invoice is sent out
a search is done to open the form based on the SO# so that the invoice data
is entered. When a payment is received same routine. The problem is that when
a payment is posted the person entering the payment may forget to search for
the next SO# and mistakenly enters the payment to the wrong SO#.- Hide quoted text -
- Show quoted text -
The description is not making sense.
If the tab/subform is in a parent child relationship then when they
are making payments they should not be entering another SO search.- at
least not from that tab since they are already sitting on an SO. But
then again I cannot see it so that may explain why I am getting
confused.
Are payments coming in and being posted to accounts by batches? In
other words when payments are being posted are they posting a lot of
payments at the same time.?
In general I would suggest you want the payment posting process to
require as few steps as possible. One form and no tabs (if possible)
or at least NOT having to go to one tab to search and another to post.
After they add the payment record, clear the form so that they are NOT
sitting on any SO or set a flag that will not allow two payments in a
row without another search (the search sets the flag off)
.
- References:
- Re: Limit Data Input
- From: Ron2006
- Re: Limit Data Input
- Prev by Date: Re: Copy record/Refigure date + 7 days
- Next by Date: Re: DLookUp Question
- Previous by thread: Re: Limit Data Input
- Next by thread: Re: Limit Data Input
- Index(es):
Relevant Pages
|
