auto advance

[7ZNJABB]

Hi Phorum,

I have a data entry form on a one-to-many set, with an embedded browse
of the child table. The last field for each record in the child is a
calculated field. When I press enter for the calc field to be entered
I would like the first field of the next record entered automatically,
in other words, the value is already there, I am just trying to save a
key press for the user. I usually do this in field rules for non-calc
fields, but how can it be done on a calc field?

Thanks for any suggestions,
efs

[forskare]

RE: auto advance

efs,

It sounds to me like you want a specific field of a new record automatically filled in after completing the calculated field of the last record. If so, is the data you want entered into the field of the new record dependent on the data in the calculated field of the lasst record?

kenn

[7ZNJABB]

RE: auto advance

Hi Ken,

Yes, it is the same field and data that is entered earlier in the PO,
so it is ready and waiting for enter or tab. In other fields that are
not calc fields, sys_send_keys does it easily.

Thank you for reading,
efs

[forskare]

RE: auto advance

efs,

What do you mean by, 'it is the same field'?
What is and where is, what do you mean by the 'PO'?
What do you mean by, 'so it is ready and waiting for enter or tab'?
Does what easily? 'In other fields that are not calc fields, sys_send_keys does it easily.'

You description of what's happening needs clarification.

kenn

[7ZNJABB]

RE: auto advance

Hi Ken,

I will try to be more specific, my earlier description left a lot to
imagination. The application crates purchase orders (POs) for a food
broker. It has a one-to-many set of orders to products and orders to
po_items, as well as tables of clients, products,and ship_to addresses.
The create order form is based on the set. The first entry into the
form when starting a PO is the PO number. Then the clients, supplier
and ship_to info is selected and filled in with popup lookup tables.
The embedded browse beneath the above header is based upon po_items
and needs to be linked to the header by a unique field, this field is
po_num which is entered earlier in the header and hence fills in
automatically into the embedded browse. Being the first field in the
embedded browse, and always being correct, I would like it to be
skipped over (but entered)automatically. The first record in the
embedded browse does that now, since the last entry in the header is
an address field and I have an event field rule on that of "sys_send_
keys("{enter}"). However the last entry of each record in the embedded
browse is a calculated field (extended Cost of "quantity*
(price-discount). Now when the enter key is pressed to conclude each
record in the embedded browse, I would like to make the first field of
the ensuing record (po_num_)be automatically entered just like the
first record. I hope this clears up the picture.

Thank you for listening,
efs

[forskare]

RE: auto advance

efs,

I'm still fuzzy on what you want but this is my interpretation....

�The first entry into the form when starting a PO is the PO number.� Is this generated automatically or manually?

�Being the first field in the embedded browse, and always being correct, I would like it to be skipped over (but entered)automatically.� In the field rules, select the Data Entry tab and go to the bottom of the screen. In the Skip box, enter, .t. This will allow for the skip. I don�t know what you mean by �(but entered)automatically� if data in this field is entered in the header.

�I would like to make the first field of the ensuing record (po_num_)be automatically entered just like the first record. I hope this clears up the picture.� Why not use the auto increment feature?

kenn

[7ZNJABB]

RE: auto advance

Hi Ken,

The PO number on the header comes from the customer, not generated by
the user, and it is the same number in the embedded browse allowing it
to become the linking field for the set.

efs

[martinwcole]

RE: auto advance

One potential to avoid is creating a situation preventing you from arriving at the field - like you want to change the value, but your "rule" won't let you arrive.

If the first field in the browse is the po, it should be easy:

If I understand:
You have an existing customer as the record in the parent table of the set, probably the top half of the form.

You have a child I'll call [purchases] in an embedded browse, probably on the bottom half of the form.

You are entering multiple orders for that customer, in the embedded browse, and all orders are using the same "purchase order number." Therefore, each new order should have the same PO.

I can think of more than one way to do this, but here is one:

Say the name of the form is "Orders".

on the orders form, put a global variable "vPONumber" �at the top of the form, the big �V�

go to field rules for the "purchases" table, and at the
CanSaveRecord event for the table, (at the very top of field rules,) put:
if is_object(":orders") 'if we are using that form
---t=table.get("orders")
---var->vPONumber=t.purchaseorder
end if

OnEnterRecord event
if is_object(":orders") 'if we are using that form; also be sure to use the colon
---t=table.get("orders")
---t.purchaseorder=var->vPONumber
---:orders:browse1.nextfieldnameonbrowse.activate() 'this achieves the "skip this field" effect
end if

this immediately refreshes the browse. You could also use this for the date, too.

[7ZNJABB]

RE: auto advance

Hi,

let me explain more. It is a food broker that uses the application.
He receives orders from a customer (who supplies the PO number)by fax
and then fills out the PO form and faxes it to the supplier. The
header of the form has name address etc of the supplier to which the
PO goes to, the bill to name addy etc, and the ship to name addy etc.

The bottom is an embedded browse whose first field is PO number, so it
can be used as a link for the set. Following is qty, stock_num,
description, price, discount, and finally the extended cost of qty*(price-discount) as the last field of the record.

The last field filled in before the first field of the first record of
the browse is a standard character field and it was easy to put
sys_send_keys("{enter}") in the onit event to click PO number into the
table.

Nowwwwwwww, here is what I want to do, since the last field of
each record in the embedded browse is a calc field, I have not found
the equivalent of sys_send_keys (to add tab or enter)for the PO number
in the first field of the next record. At present the user must hit
tab or enter before she can enter the qty. This thing is working very
well, I am just trying to save her a key punch. Whewwwwwwwww !

efs

[martinwcole]

RE: auto advance

if PO is the linking field for the child to the parent, then the parent has a PO field, too. So, don't put the po on the browse! - since it will always be the same as the parent!

[7ZNJABB]

RE: auto advance

Hi Martin,

It seems to me that if the PO number is not in the child, I'll get all
of the products from all of the records that are in the PO_items table
for what ever other field is used for linking. Am I in left field?

efs

[JohnZaleski]

RE: auto advance

Martin is not saying don't have it be a part of the child record. He is saying you don't have to include it on the browse since Alpha automatically fills in the field according to your set definition. If its not showing on the browse, you don't have to skip it.

[7ZNJABB]

RE: auto advance

OOPS, why didn't I recognize that. Thank you.

efs