Bill-
I believe it might be due to the default Office 2003 VBA security settings
that "do not trust unsigned VBAapplications" by default. You can download
the free Microsoft Office Resource Kit (ORK) at:
http://office.microsoft.com/en-us/FX011511471033.aspx
to allow you to easily change the Office 2003 VBA security settings.
Jerry



"Bill@DOT" wrote in message
...
Hello,

I have an Excel 2003 spreadsheet/VBA application that is used to export
data
to customers from a central database. The spreadsheet includes VBA macros
that facilitate viewing of the spreadsheet and allow the customer to
modify
data. The macros are signed using an Office 2003 digital signature. The
workbook data is not signed.

The spreadsheet also includes an upload function that emails a spreadsheet
(that was modified by the customer) back to a central mailbox where I use
a
SQL server, ISQL, C# batch application to automatically extract the data
and
update our database. After extracting the spreadsheet from an uploaded
email
message, the automated process opens the spreadsheet with an argument that
tells it to self-extract its data to a text file. The extracted data is
then
loaded into SQL server for processing.

This process has been working great until recently. I added a few new edit
routines that aren't even executed when the problem occurs. Now when I
attempt to do the self extraction process for an uploaded spreadsheet, I
get
the following error:

"The macros in this file do not match the digital signature. Only a macro
virus would cuse this. Please scan for viruses, and notify the publisher
of
this document. Macros will be disabled."

I'm pretty sure this is not a virus. I've created 2 test spreadsheets,
Test1.xls and Test2.xls, that will demonstrate this problem (email me if
you'd like copies of these spreadsheets). The spreadsheet's macros are
signed
with an Office 2003 digital certificate. The only difference between the
two
spreadsheets is that Module1 in Test1.xls contains 5 Subs and 1 Function.
Only the first 2 Subs are actually executed in the test. Test2.xls only
contains the first 2 Subs.

To run the test, you open one of the spreadsheets, click Do Test, close
the
spreadsheet, click Yes when promted to save the changes and then reopen
the
spreadsheet. Test1.xls gets the above errror. Test2.xls does not get the
above error. Again, the only difference between Test1.xls and Test2.xls is
that the last 4 routines that are in Test1.xls Module1 are not in
Test2.xls
Module1 and these routines are not executed when Do Test is clicked.

It doesn't make any sense why this would be happening. Help!