SQL is the back-end in both cases, right? Presumably identical indexes and SP's?

I'm game.

>This is what I propose to begin with...
>
>I will need help from someone to create the VFP code. I'll handle the .NET end of things.
>
>Who would like to volunteer?
>
>Database (I will provide a download to a sample database)
> A customer table with 1,000,000 records in it.
> This data will be stored in SQL Server and a VFP DBC
>
>Retrieve data from a datasource.
> .NET will use SQL Server as its data source
> VFP will use the DBC natively.
>
>Filter that set of data based on some criteria.
>1. A simple search screen that allows a user to query the customer data by
>a. Lastname and firstname – sorted by lastname, firstname
>b. Zip Code and Last Name
>
> User should be able to subselect the data once it is in the client
> By state would be a good example of this.
>
>Results will be displayed in the native grid to the tool being used.
>
>
>Sort that data based on some criteria.
> After the data is retrieved it should be sortable in the interface.
>
>Display that data in a UI
> UI should allow for selection of a customer record and bring that record into a data entry screen.
> Date fields use date pickers
> Any relevant Drop down data will use a Combo box
> Numeric fields will use a masked type of editor.
>
>Edit that data via a form
> The UI will have the ability to update the selected record.
>
>Add new data via a form
> The UI will have the ability to add new data to the database.
>
>We should also include some type of bulk DML..What would be a good example of DML in this case?
>
>
>All items must be benchmarked some how. – we'll need to figure out how to time this.