Yes, it is very important for me that the WinForms application have the same look and feel as VFP application. The customer who ordered this conversion mainly ordered it for the sake of having SQL Server backend. They are happy with the UI and do not want it to change. I could have easily done this conversion leaving the UI in VFP and most likely the customer would not mind. But I took the opportunity to invest my time and learn WinForms.

>There are many ways to accomplish this ... one of the questions you might ask yourself is whether you want your .NET app to have a similar look-and-feel as your VFP app (are you doing a conversion of your VFP app? or do you just mention your VFP app to describe how you did it before?)
>
>I don't think there's really a .NET way vs a VFP way distinction. It's all about how you want it to work ... I guess this is a cop-out answer, eh? <g>
>
>~~Bonnie
>
>
>
>
>
>>Hi,
>>
>>In my VFP app I have a lookup control (Account #) which is a container with textbox and a button. On click of the button a separate form pops with a grid showing accounts. User selects an account and clicks on Ok button.
>>
>>In a WinForms application, do you suggest creating a User Control (with a textbox and a button)? And then also pop-up another form with a grid?
>>In terms of getting the data from a table for this control, do you suggest that a typed dataset for this look-up control (list of accounts) be filled in the INIT method of the look-up control? Is this how it is done in .NET WinForms?
>>
>>TIA.