Access 2003 and Excel 2003

[JamieJamie]

Hi

New to this group and being really cheeky and seeking an answer to my
first question but a bit desperate so hope someone can help.

I have written a large application in Access 2003 for a medium sized
pc repair company. The application uses Excel libraries to produce
certain reports in Excel format. The front end is all Access (with
lots of VB) and the backend is SQL. The front end is distributed via
lines in a login script.

My problem is this. The front end is distributed to 50 + pcs with
Microsoft Office 2003 installed locally on each machine. Not all the
PCs run the Excel reports. It turns out, we do not have Office 2003
licenses for all the PCs but we do have Access licenses for all PCs.
After removing Excel, the Access application I wrote crashed! It would
be an enourmous pain to have 2 versions of the databases, so was
wondering how to avoid auditor scrutiny without crashing the database
on PCs without Excel.

Help!!!

 

[Beth Melton]

In short, you can't. If you are automating Excel then the Excel Object
Library needs to be available. To get the Excel Object Library it needs to
be installed. Additionally, an Excel a license is required even if another
program is calling it and using it.

Now, if the PCs that don't have Excel aren't using the Excel functionality
then you should be use late binding, instead of early binding, which should
prevent the error.

Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

Coauthor of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/books/9801.aspx#AboutTheBook

Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/

 

[Steve Rindsberg]

This might better be posted to one of the Office dev groups
(Office.Developer.VBA or the like)

But before doing that, you might want to trace code execution and in your post,
quote at least the line (and some surrounding ones) where the error occurs, and
any error message or error description.