So long as you develop it in 2000 then it will be compatible with 2003, as
opposed to the other way around where you could introduce features which are
not supported. So long as it works for the lowest version you will be good to
go for all users. After that it does not matter what version it is saved in,
unless one of your clients introduces features which are not supported, saves
the file and sends it back then you will have to clean that up.
--
HTH...

Jim Thomlinson


"BhavdeepSachdev" wrote:

Thanks Jim,

The project I am working on requires multiple saves for the same file by me
and the client. (i.e. I save the file & send it to the client, the client
makes changes and saves it and sends it back to me. This process is done
multiple times)

I can develop and save the file in Excel 2000, but some of the clients have
Excel 2003 too. When they save it and send it back to me, I will get the
"Compile error in hidden module"

Any suggestions ?

Thanks,
Bhavdeep.

"Jim Thomlinson" wrote:

You should always develop for the lowest version of Excel that you anticipate
will be running. In your case this should be done in Excel 2000, otherwise
you will continue to get errors. As for Late binding you should never do
that. Just because you can do it does not mean you should. VBA allows a lot
to things that are just not good. Check out this link (near the bottom of the
page) for an explanation...

http://www.cpearson.com/excel/variables.htm
--
HTH...

Jim Thomlinson