Excel SaveAs Overwrite message

I am writing a DXL script to export DOORS data to Excel. At the end, I am calling the Excel SaveAs function. If the file already exists, I get a message dialog "Do you want to overwrite this file ?", to which I always reply "Yes". Now, I want to execute the same script in batch mode. So how can I prevent getting this message ?
 

/*
 * This function saves the file as the passed in file name.(From ExcelFunctions.inc)
 */
bool saveFileAs(string filename) {
   if(fileOpen) {
      clear(args);
      put(args, "FileName", filename);
      
      if (excelVersion == "Excel.Application.12") {         // If Excel version is 2007
        put(args, "FileFormat", "56" );     // Save file as Excel 97-2003 .xls format
      }
        
      if(!checkResult(oleMethod(objWorkbook, "SaveAs", args))) {
         errorBox("File SaveAs failed.");
         return(false);
      }
      
      return(true);
   }
   
   errorBox("File not open");
   return(false);
}

Re: Excel SaveAs Overwrite message
OurGuest - Tue Aug 02 11:47:05 EDT 2011

Re: Excel SaveAs Overwrite message
OurGuest - Tue Aug 02 13:02:31 EDT 2011

Re: Excel SaveAs Overwrite message
llandale - Tue Aug 02 13:29:33 EDT 2011

Don't know about your dialog problem from Excel; but I'd be tempted to just delete the file in DXL before commanding Excel to save it.
.... if (batchMode()) deleteFile(NameFile) // ignore no-such-file errors
This lets you respond to the prompt interactively but prevents the prompt in batchmode.

Your "errorBox" functions will likewise cause your DXL to stop in batchmode. That's actually a rather big problem. Perhaps this will work:

void  errorBox_Temp(string Message)
{            print "in 'errorBox_Temp()'\n"
   if (batchMode()) //
   then print Message "\n"
   else errorBox(Message)    // Call the standard "errorBox"
}  // end errorBox_Temp()
 
void errorBox(string Message)
{   // Override function of standard "errorBox"
             print "in overrride 'errorBox()'\n"
    errorBox_Temp(Message)
}   // end override errorBox()
errorBox("hello")  // debug

However, all "print" statements in batchMode will cause an additional command prompt window with all the prints, and when your batch program naturally stops, DOORS will linger until the next morning when you read the errors and close the window. So maybe instead of "print" you instead append to some error file.

Then there is "ack" and "confirm" and "query" and "infoBox" and "warningBox" bla bla bla. "confirm" and "query" can be overrided to always give the 1st response, and then your code has to be written such that the first response works well in batchmode.

Yup, its messy to have code that can run in batchMode and interactively.

• Louie

Re: Excel SaveAs Overwrite message
David_G_Bond - Wed Aug 03 10:31:06 EDT 2011

void  errorBox_Temp(string Message)
{            print "in 'errorBox_Temp()'\n"
   if (batchMode()) //
   then print Message "\n"
   else errorBox(Message)    // Call the standard "errorBox"
}  // end errorBox_Temp()
 
void errorBox(string Message)
{   // Override function of standard "errorBox"
             print "in overrride 'errorBox()'\n"
    errorBox_Temp(Message)
}   // end override errorBox()
errorBox("hello")  // debug

• David Bond

Re: Excel SaveAs Overwrite message
llandale - Wed Aug 03 13:54:01 EDT 2011

• Louie