I definitely wasn't being descriptive enough!

What I mean by key control is typically a container with a textbox and command button.

Anywhere on the form where there is a lookup (foreign keys typically), the user can "drill down" to find the correct value for the field. In a Customer/Invoice scenario, you first "drill" on the customer, then either amend or edit an invoice. Both would have these drill down containers. The Drill Down itself is really the find form.

The only time you can add is if you look first. Type in a value that's in the table brings up the rest of the record. If not, invoke the drill down....The add button is typically on the "find" form. I've seen many commercial apps set up like this and it makes sense because you are forcing the user to see what's out there first before adding. On a foreign key field, if the user wants to add, it would launch it's own Maintenance Form.

I have to design the forms to bring up enough information for the user but never too much because I'm dealing with a lot of data and about 20 remote locations.

There are really two scenarios. One for the primary maintenance forms (say Part Number Maintenance) and one for the foreign key lookups.

Am I making sense?


Chuck


>How do you guys handle large data sets within the framework? If I have a 100,000 record SQL table that I want to add a new record to, typically I would want the user to "find" something that closely matches first, then allow an add. This helps to elimate typo mistakes when adding a record.
>
>With this in mind, from the key control, I could also let the user do a leading search to see similiar records, then add if they see nothing to edit.
>
>Hopefully I'm making sense. Has anyone run into similiar situations? Does the Framework handle this natively?
>
>Thanks,
>
>Chuck

Let me phrase it my way and see if we're both saying the same thing, ignoring the large data set for the moment:

You don't want to have the user add a new record without first checking if the info already exists. If the data doesn't already exist it can be added.

What do you mean by key control? Is this is the current index of your data?
Is a leading search an incremental search thru the list tab grid of currently existing info?