set ExcelApp to new Application()
set ExcelWorkBook to ExcelApp::Workbooks::Add(1)
set ExcelWorkSheet to ExcelWorkBook::Sheets[1] as type Worksheet
set ExcelWorkSheet::Cells[1,1] to "test"
invoke ExcelWorkBook::SaveAs("C:\\temp\\test1.xlsx")
invoke ExcelWorkBook::Close()
invoke ExcelApp::Quit()
The above code works in C#, not sure what is going on with Visual Cobol. I get
+2set ExcelApp to new Application()
set ExcelWorkBook to ExcelApp::Workbooks::Add(1)
set ExcelWorkSheet to ExcelWorkBook::Sheets[1] as type Worksheet
set ExcelWorkSheet::Cells[1,1] to "test"
invoke ExcelWorkBook::SaveAs("C:\\temp\\test1.xlsx")
invoke ExcelWorkBook::Close()
invoke ExcelApp::Quit()
The above code works in C#, not sure what is going on with Visual Cobol. I get
Can you show me how the data items are defined as well?
Thanks
set ExcelApp to new Application()
set ExcelWorkBook to ExcelApp::Workbooks::Add(1)
set ExcelWorkSheet to ExcelWorkBook::Sheets[1] as type Worksheet
set ExcelWorkSheet::Cells[1,1] to "test"
invoke ExcelWorkBook::SaveAs("C:\\temp\\test1.xlsx")
invoke ExcelWorkBook::Close()
invoke ExcelApp::Quit()
The above code works in C#, not sure what is going on with Visual Cobol. I get
It might be useful to see the equivalent C# as well. One thing that occurs to me is that subscripting using square brackets is zero-based in COBOL, just as in C#. Is it possible that you meant to reference Sheets[0] and Cells[0, 0] ?
Robert.
set ExcelApp to new Application()
set ExcelWorkBook to ExcelApp::Workbooks::Add(1)
set ExcelWorkSheet to ExcelWorkBook::Sheets[1] as type Worksheet
set ExcelWorkSheet::Cells[1,1] to "test"
invoke ExcelWorkBook::SaveAs("C:\\temp\\test1.xlsx")
invoke ExcelWorkBook::Close()
invoke ExcelApp::Quit()
The above code works in C#, not sure what is going on with Visual Cobol. I get
01 ExcelApp type Application.
01 ExcelWorkBook type Workbook.
01 ExcelWorkSheet type Worksheet.
Sorry, it would have made sense to add them. Thanks
set ExcelApp to new Application()
set ExcelWorkBook to ExcelApp::Workbooks::Add(1)
set ExcelWorkSheet to ExcelWorkBook::Sheets[1] as type Worksheet
set ExcelWorkSheet::Cells[1,1] to "test"
invoke ExcelWorkBook::SaveAs("C:\\temp\\test1.xlsx")
invoke ExcelWorkBook::Close()
invoke ExcelApp::Quit()
The above code works in C#, not sure what is going on with Visual Cobol. I get
Application ExcelApp = new Application();
Workbook ExcelWorkBook = ExcelApp.Workbooks.Add(1);
Worksheet ExcelWorkSheet = (Worksheet)ExcelWorkBook.Sheets[1];
ExcelWorkSheet.Cells[1, 1] = "test";
ExcelWorkBook.SaveAs(@"C:\\temp\\test1.xlsx");
ExcelWorkBook.Close();
ExcelApp.Quit();
Here is the C# code.
+2set ExcelApp to new Application()
set ExcelWorkBook to ExcelApp::Workbooks::Add(1)
set ExcelWorkSheet to ExcelWorkBook::Sheets[1] as type Worksheet
set ExcelWorkSheet::Cells[1,1] to "test"
invoke ExcelWorkBook::SaveAs("C:\\temp\\test1.xlsx")
invoke ExcelWorkBook::Close()
invoke ExcelApp::Quit()
The above code works in C#, not sure what is going on with Visual Cobol. I get
We were able to reproduce the problem and a fix has been created.
The problem is occurring because the SaveAs method uses optional parameters, as do a number of these Interop methods and if not actually supplied to the method the compiler was generating a null parameter instead of the expected value of System.Reflection.Missing::Value.
Please create a support incident and place my name in the description and I will ensure that it gets registered against the rpi so that I can get a fix to you when available.
In the meantime you can workaround the issue by specifying the parameters as follows, although you might have to do this for other Excel Interop methods as well.
invoke ExcelWorkBook::SaveAs("\\temp\\test1.xlsx"
type System.Reflection.Missing::Value
type System.Reflection.Missing::Value
type System.Reflection.Missing::Value
type System.Reflection.Missing::Value
type System.Reflection.Missing::Value
type XlSaveAsAccessMode::xlNoChange
type System.Reflection.Missing::Value
type System.Reflection.Missing::Value
type System.Reflection.Missing::Value
type System.Reflection.Missing::Value
type System.Reflection.Missing::Value
)
Thanks
set ExcelApp to new Application()
set ExcelWorkBook to ExcelApp::Workbooks::Add(1)
set ExcelWorkSheet to ExcelWorkBook::Sheets[1] as type Worksheet
set ExcelWorkSheet::Cells[1,1] to "test"
invoke ExcelWorkBook::SaveAs("C:\\temp\\test1.xlsx")
invoke ExcelWorkBook::Close()
invoke ExcelApp::Quit()
The above code works in C#, not sure what is going on with Visual Cobol. I get
I copied and pasted your code and I got the same message. I then changed the filename parameter to be an absolute path and it worked. Apparently relative paths don't work with the saveas method.
Just incase somebody else was interested here is the code to get the drive letter.
set myString to type Environment::CurrentDirectory()
set myString to type Path::GetPathRoot(myString)
set myString to myString & "temp\\test1.xlsx"
I will create a support incident for this asap.
set ExcelApp to new Application()
set ExcelWorkBook to ExcelApp::Workbooks::Add(1)
set ExcelWorkSheet to ExcelWorkBook::Sheets[1] as type Worksheet
set ExcelWorkSheet::Cells[1,1] to "test"
invoke ExcelWorkBook::SaveAs("C:\\temp\\test1.xlsx")
invoke ExcelWorkBook::Close()
invoke ExcelApp::Quit()
The above code works in C#, not sure what is going on with Visual Cobol. I get
I also had a problem with relative path, but I actually found that when I did pass a relative path to SaveAs it was using the setting of the USERPROFILE environment variable as the path base. I didn't investigate further and don't know why this is the case...
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
