Hi,

I recently upgraded to Excel 2003 from Excel 2000. My client still uses the
Excel 2000 version.

There is a lot of VBA programming in the file (both at the worksheet level
as well as classes and modules).

After I started saving the file in Excel 2003 version, when the client
(using Excel 2000) opens the file, they get the error "Compile error in
hidden module" for two different modules.

I did some research on google and this is what I found out:
When I save the file in 2003 version, the client's computer (Excel 2000)
looks for the 2003 Type Library (.olb file), does not find it, and displays
the error.

Here are the options that I have currently:
1. Use Late Binding - But this would require a lot of changes in the code
2. Downgrade my version to Excel 2000 and start saving the files in that
version.

Do any of you have any other suggestions ?

Here is one thing I tried that didn't work: Save the file for a previous
version as "MS Excel 97 - Excel 2003". - Opening in Excel 2000 still gives
the error. This does not attach the new type library.

And another problem is that the type libraries (olb files) are NOT
redistributable.

I am looking forward to all the suggestions.
Thank you,
Bhavdeep

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


"BhavdeepSachdev" wrote:

Hi,

I recently upgraded to Excel 2003 from Excel 2000. My client still uses the
Excel 2000 version.

There is a lot of VBA programming in the file (both at the worksheet level
as well as classes and modules).

After I started saving the file in Excel 2003 version, when the client
(using Excel 2000) opens the file, they get the error "Compile error in
hidden module" for two different modules.

I did some research on google and this is what I found out:
When I save the file in 2003 version, the client's computer (Excel 2000)
looks for the 2003 Type Library (.olb file), does not find it, and displays
the error.

Here are the options that I have currently:
1. Use Late Binding - But this would require a lot of changes in the code
2. Downgrade my version to Excel 2000 and start saving the files in that
version.

Do any of you have any other suggestions ?

Here is one thing I tried that didn't work: Save the file for a previous
version as "MS Excel 97 - Excel 2003". - Opening in Excel 2000 still gives
the error. This does not attach the new type library.

And another problem is that the type libraries (olb files) are NOT
redistributable.

I am looking forward to all the suggestions.
Thank you,
Bhavdeep

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

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