MS Office Controls: Cool or Fool?

[ljlevend]

I just realized that it is possible to add MS Office Controls to a Windows Form, just like any other ActiveX Control. I haven't worked with the controls much, but it seems like the controls can do exactly what I want. (In fact, I was hoping to make a DataGrid and an MSChart seem like they were Worksheets and Charts from Excel.) On the other hand, I can anticipate some major compatibility and/or copyright issues. So now I have a big question ... would I be cool if I used MS Office Controls in my app, or would I be a fool? (For the sake of this discussion, please assume that all of my users have the required version of MS Office.)

Thanks a bunch! Lance

[pgrimes]

For the sake of this discussion, please assume that all of my users have the required version of MS Office

If everyone that uses the site really does have the required vers. of Office than you are moderately cool

Microsoft has some pretty strict licensing issues on using Office Web Components in the Internet-world (as well as on an intranet).
Read here:http://support.microsoft.com/support.../Q243/0/06.asp


So, if they don't have office...

U = Fool

[ljlevend]

This would be a Windows Application, not something that runs over the web. Does that change anything?

[hellswraith]

I don't think anyone here is an expert on whether MS will slap you around if you do that, the best way to know is to formally write to them and ask them whether it is ok or not. I am pretty sure though that you can't redistribute their dll files, so the users of your app would definately NEED office to be installed for you to use those dll's in your app....but again, I am no expert, check with the almighty...lol

[ljlevend]

Thanks for the advice. Guess I'll be contacting MS.

Can any of you give some opinions about long term compatibility issues? For example, would I ever regret using an Excel Worksheet rather than a DataGrid or an Excel Chart rather than an MSChart? Note that I would only be displaying measured data on the Worksheets and Charts. I'd still use a database for the Employee Name, Date of Hire, Salary... type stuff. Also, the first question that most users ask in my field is "can I convert it to Excel?"

[hellswraith]

Also, the first question that most users ask in my field is "can I convert it to Excel?"

What I would do is not rely so heavily on Excel. Show the data is a DataGrid inside your app, and include a way to export to an Excel file when needed. This would make it so you just have to update the export code when a change needs to be made (new versions of office...ect.). If you used Excel throughout the whole app, then you would have to go through all your code and update if there was ever a change with office.

Also, it wouldn't require office to be installed on the user system to use your app, it would just need to be installed if they wanted to use the export feature of your app.

[pgrimes]

good idea hellswraith, I would try to go that route.

[ljlevend]

guess I'll use a DataGrid then. thanks for the advice!