>1. In our application we compile our EXE but keep one class library separate so we can use the same EXE but different user interfaces to the database. Is there some sort of equivalent in C#? I'm thinking of either a DLL or Assembly that can be created separate from the compiled EXE, yet referenced by the EXE and used. In this way we can maintain our ability to customize the database without having to customize the EXE for each client. Can it be done? Are there any articles or topics you could point me to to learn more? Thanks.

Absolutely, and it is somewhat of a standard approach to n-tier development in .NET. Simply add a new Class Library project to your solution, and in your front-end project add a reference to this class library. Let us know if you need more guidance.

>2. We import and export to Excel, Dbase, CSV, etc. We've been using the COPY TO TYPE XLS command in FoxPro. Is there a class, DLL, assembly or whatever we can use in .NET to do the same basic things?

It depends on how exactly you want it import, and what you want to import. For example, with a .csv file you can create an connection and fill a dataset, but sometimes it is easier to open the file with a filestream and parse it manually. If you Google things like "Import Excel file in .NET" you should find plenty of examples.

>3. We built the Report Designer into our application because we wanted a close tie with our internal query builder. As a result, end users, etc. can create their own reports with the functionality of the FoxPro report writer. I wonder if its possible to include the Crystal Reports designer into your EXE? Or for that matter, has anyone had any experience with any of the commercially available report desigers that you can include in your EXE...recommendations?

I can't help you here... sorry.

>Well, thats about all I can think of for now. We have 10,000s of lines of code to convert and that should keep us busy til next year some time.

Have fun. I don't know the situation in your organization, but you could probably benefit from a .NET expert as an employee or a consultant. Sometimes it takes a few applications and months to really *get* the .NET way of doing things, and by that time you might have a bunch of stuff re-coded in a less than optimal way.