Since you're using SQL Server, I would investigate Reporting Services. Price is right at free.

>>You should separate the data access from the business rules. Create separate DLLs. Also, .Net applications are typically architected differently than standard VFP apps. Inheritance is not as heavily used, but aggregation is used much more. Perhaps some research on .Net architecting would help.
>>
>>Instead of using VFP for reporting, you may want to look at Crystal Reports or SQL Server Reporting Services.
>
>Craig,
>
>Thank you for the reply!
>
>Kevin said the same thing about business rules and data access.
>
>Where would I find good reference on .Net architecting?
>
>I hear Crystal Reports is costly to distribute. Is that not true?