I'm looking for a best practice approach to the following application
life-cylce:

1. Active Server Page (ASP) has file system access to an Excel File with an
embedded VBA Macro

2. The ASP page opens the Excel File, allows the auto macro to be invoked.
The VBA code does some altering of the Excel File.

3. The ASP page then saves a copy of the file, but first strips out
(removes) any VBA Macro code. The file that is saved is the just the VBA
processed data.

I've had success automating Excel with VBScript code inside the ASP page,
but this process requires that the VBA Macro live inside the Excel file.