Bob,

Call me! We should talk about some of this. Perhaps lunch in the next week or two?

>Hi all,
>
>We are happily converting our major application to .NET as a result of the recent announcement...and I have a number of general questions which I can hopefully be pointed in the right direction.
>
>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.
>
>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?
>
>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?
>
>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.
>
>Bob Bartel