Terry,

That is something that I will check out in the 'Solutions Samples' application included with VFP.
Thanks for the suggestion.

>My two cents:
>In cases where the data entered will be static - IOW - the number of records and the field contents remain fairly constant [and rarley edited] (like a lookup table), then a grid is appropriate. If the data is new data, or lots of data, or gets a lot of edits, then a grid might be better suited as a navigator/browser. But Tree Views and ListViews (activeX) make great navigators too!
>
>An over-reliance on grids by some may have given VFP a bad rap. ListViews are kool. When a node is selected, populate TextBoxes with field data for edit or appending. Live sliders, flash sorts on all columns (none of that snap to stuff and no tags required).
>
>In your project, the color and size data could be a seperate table from which the user could select to create a "quantity" transaction in another tabble.
>
>Combo for Color
>Combo for sizes
>Enter Dates and Quantity in textboxes and write to transaction file. Range your transaction list by date if the need to be in a browse list or navigator!
>
>
>Thats my two cents!
>
>
>>I have read here, in the past, that grids should not be used for input.
>>What are the recommendations for the typical retail clothing application where the input (if a grid was used) would look something like this:
>>
>>xxxx = user inputs style #
>>999 = user input qty for the specific colour/size
>>
>>Thanks in advance.
>>
>>
>> Colour Colour
>>Style size size size size size size size size
>>
>> Black Red
>> 2 4 6 8 2 4 6 8
>>
>>xxxxxxxx 999 999 999 999 999 999 999 999
>>xxxxxxxx 999 999 999 999 999 999 999 999