Reading values from Excel file and changing Label text at runtime (Interop or oledb?)

Question

0.00/5 (No votes)

See more:

I have upto hundred alarms displayed on form. I want to change the Label text of
Alarm at runtime if customers want to change.

so I have right now used Excel object library 12.0 to read values() from excel file.
and change the text of alarms Labels

customer can modify number of alarms, its text in excel file ,save where he wants
and then import it to change label text at runtime.

So my question is it good to use dll(excel 12.0 object library reference) or I should OLEDB i.e by database to import the file(values).

because there is lots of TYPE.MISSING in Excel and are there any chances of crashing the file because of version of MS Excel i am using and the customer may have different version.

Thankyou in Advance.

Posted 15-Apr-14 3:51am

krishpraj123

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

James_Finch · Answer 1 · 2014-04-15T09:35:00

Personally I would use interop, since if you are creating Excel files the end user probably needs to use them and will have some version of Excel installed. Even if she / he doesn't need to view them they will probably have Excel. :)

You don't need to know which version the user has installed, except maybe for the file extension on save. Here's a little snippet from some code I used to set the variables on a SaveFileDialog instance which allowed the user to specify a save location:

C#

Microsoft.Office.Interop.Excel.Application excelApp =
                    new Microsoft.Office.Interop.Excel.Application();
                string strVersion = excelApp.Version;
                string[] strsVersion = strVersion.Split('.');
                int version = Convert.ToInt32(strsVersion[0]);

                if (version >=12)
                {
                    sfd.Filter = "Excel Workbook|*.xlsx";
                    sfd.DefaultExt = "xlsx";
                }
                else if (version > 0 && version < 12)
                {
                    sfd.Filter = "Excel Workbook|*.xls";
                    sfd.DefaultExt = "xls";
                }
                else
                {
                    // No version installed
                }

Here you can see the SaveFileDialog (sfd) being set up to add the proper path + extension to sdf.FileName. This is later used to save the spreadsheet in this way:

C#

eWorkbook.SaveAs(OutputPath,
    Microsoft.Office.Interop.Excel.XlFileFormat.xlWorkbookDefault);
eWorkbook.Close(true);

Note the lack of Type.Missing arguments: they are optional. OutputPath was defined by the user using sfd.