Ben

It shouldn't be. If you were going the other way, there could be some
compatibility issues, but developing in a lower version should cause no
problems at all.

The first thing I would try is (from 2000) to export all the modules, delete
them, then reimport them. Then recompile and Save. Send that over to him
and see if there's something in the code that's screwing it up.

If that doesn't work, you might try round-tripping the workbook through
HTML. Save it as HTML, the open the HTML and save back as an Excel
Workbook. If there's some corruption in the workbook, that may get rid of
it.

--
Dick Kusleika
MVP - Excel
Excel Blog - Daily Dose of Excel
www.dicks-blog.com

"Ben P" <Ben wrote in message
...
I have developed an application in Excel 2000 (SP3) for a colleague using
2003. The main bulk of the application is moving data around, although
there
is some charting.

When my colleague tries to open the workbook he gets the usual secuirty
warning about opening the book with the macros in and then gets an error
message saying that Excel has encountered a problem and has to close. If
you
reopen it Excel tries to 'repair' the problem by removing the VBA.

Is this a compatibility issue?

Thanks,
Ben