SaveAs, Error.

[JapanDave]

I am getting an error after saving a workbook,

Error opening file: "The file format differs from the format that the file name extension specifies"

I save the book as an ".xlsx" file and when I go to open it up it prompts me for this error. I click open anyway and I am greated with a blank file. No grid just the tool bar.

Any ideas?

[JapanDave]

Nothing????

[YasserKhalil]

Try exporting the workbook to the same extension of original workbook ..
You may have corrupted export process for the workbook ..

[JapanDave]

It is a completely new workbook create via code.

[YasserKhalil]

Can you post the code used to examine it?

[JapanDave]

OK, this creates and closes the file.

private static void CreateWorkbook(string fileName, string macro)
        {
            try
            {

                if (File.Exists(fileName)) { File.Delete(fileName); }

                GC.Collect();             

                var excelxl = new Excel.Application();               
                Excel.Workbook workBook = excelxl.Application.Workbooks.Add();               

                var sheet = (Excel._Worksheet)workbk.ActiveSheet;                           
                var module = workBook.VBProject.VBComponents.Add(VBIDE.vbext_ComponentType.vbext_ct_StdModule);
                module.CodeModule.AddFromString(macro);
                excelxl.Visible = false;
                excelxl.UserControl = false;                
                workBook.Close(true);
            }
            catch (Exception ex)
            {                
                Alerts.Error("File was not created", "Error", ex);
            }

        }

Don't know if that helps any?

[JapanDave]

double post.

[YasserKhalil]

This is not VBA code ..!!!

[JapanDave]

@YasserKhalil , I didn't say it was. But the fact remains that I have this problem when opening the file.

[nilem]

Hi JapanDave (good to see you again )
Just as a guess, maybe

Excel.Workbook workBook = excelxl.Workbooks.Add();

instead of

Excel.Workbook workBook = excelxl.Application.Workbooks.Add();

[JapanDave]

@nilem, You too,

But , my code already does that,

Excel.Workbook workBook = excelxl.Application.Workbooks.Add();

[nilem]

I meant to exclude Application statement from Excel.Workbook workBook = excelxl.Application.Workbooks.Add();

[shg]

module.CodeModule.AddFromString(macro);

I save the book as an ".xlsx"

You're adding a code module to a new blank workbook, and then saving it with an xlsx extension. Xlsx files can't contain code, so I'd expect Excel to be surprised.

It's the same result you'd expect if you renamed an xlsm file to xlsx.

[JapanDave]

@shg, Crap, I forgot to delete the module, that fixed it.

@nilem, OK, I see what you mean. As I said above it was the code module not being removed.

Thanks Guys!

[JosephP]

how come you don't save the workbook explicitly using the file name? then you could specify the format too

[JapanDave]

@JosephP, I was doing that, but dropped the extension so as to save the excel file that is native to the office version that the user is using.

And that has me thinking, if you specify the extension as say an ".xlsx" won't any code module be automatically dropped?

[JosephP]

only if you specify the correct fileformat parameter

[JapanDave]

Well, deleteing the module did not work. Still getting the same error. This is frustrating. Also, it only happens on Windows 7 machines. Windows 8 and above does not cause this error.

[JapanDave]

Still getting this issue, no matter what format it is saved under it creates a corrupted file.

So, I thought screw it, I will save it in PDF format, as I am only making the file so it can be printed out in the format I want.

[JapanDave]

Well I figured out what has been happening. When after saving the file and closed it, I had released all the objects, but it was leaving a background process running, which was linked to a now closed file and therefore not allowing anything else to open. And anything that was opened was met with different file error. So I had to loop through all the process ID's of the current running excel processes and find the one that should not be there and kill it.

This seems to be a Com Object related issue with Excel Interop. Deffinately not a typical issue with releasing Com Objects in C#,but in certain situation can cause this kind of issue.