Hi,

The we are having is that once we install our custom Excel application on
the clients setup it fails to run the .Net code. The application is an Excel
spreadsheet which calls a bin directory with .Net DLLs in it. It runs fine
under office 2003 professional complete install.

The client is running active directory and have Office 2003 Standard rolled
out automatically. The client has a requirement that Access 2003 is NOT
installed, as they are currently in the process of testing the migration of
all their old Access 2000 databases to Access 2003. This will happen at a
later date.

We have been told by Microsoft that Office 2003 Standard DOES NOT support
running Excel.Net Interop applications. Is this really the case? Why?

Anyway...

The client has taken the following measures to try and circumvent the
problem.
1. Uninstall Office 2003 Standard.
2. Install .Net 1.1
3. Install Office 2003 Pro (Complete install)
4. Install "Enlighten Designs" custom software. (Excel .Net Inter-op
spreadsheet with .Net binaries)

This sometimes works, but not in every case. It does not seem to be a
reliable / consistent method for making it work.

The following steps seem to consistently fail to work:
1. Uninstall Office 2003 Standard.
2. Install .Net 1.1
3. Install Office 2003 Pro (Custom - No MS-Access, No Publisher)
4. Install "Enlighten Designs" custom software. (Excel .Net Inter-op
spreadsheet with .Net binaries)

We have tried numerous install and uninstall scenarios, including changing
the order of installation, and the components installed by Office 2003. None
of these approaches works 100% of the time. The client is unhappy with this
situation and it does not reflect well on us, or Microsoft, in our decision
to integrate .Net code with Microsoft Excel.

What I'm hoping for is an installation procedure that we can follow, that
will enable our customised Excel application to run in 100% of
installations.

Thanks in advance for your help

Flip