Hi Matt

What I do is use a 2 page pageframe. The first page has a list of records in a grid. Above the grid is a search box. The user enters criteria and hits search. The grid fills with a cursor of just the matching record and just the required columns.

The user can pick a record and switch to the second page for details. A toolbar permits navigation on either page.

Imagine a company data entry form. On the list would be things like company name, city, phone #. On the details page would be those columns and a grid for contacts.

I'd do an invoice form the same way. The list page allows searching for existing invoices. The details page of the invoice form would have a textbox for company (customer). The user's entry would be validated against a cursor of companies. The cursor is generated by another instance of the same object that produces the company list in the company data entry form. When the user makes an invalid entry or an entry that has multiple matches, the company form is launched. The company form adopts the data session of the invoice form, so it doesn't have to query company information again.

I can't post pictures right now, but when I get a chance I will.

>I always like to see another VFP app, just to see how other people design their interfaces. Would anybody be willing to post some screenshots I could see. I would be glad to share mine, but I mainly want to others. I am not snooping around to find out secret data hidden in the screenshots, I just never hardly get to see other people's work, and I thought this would be a good way.
>
>In my Job Shop sofwtare app we have the following main forms:
>
>Add/Edit an order from a customer.
> (collects cust_no, PO, del_date, area, contact, and a grid to enter line items
>
>
>Add/Edit Purchase Orders (collects the typical stuff)
>
>Order browser
>
>Search form for job line items
>
>Search form for PO line items
>
>etc...
>
>I would just like some fresh ideas to implement in any of my forms.
>
>
>Thanks.