Local / network options for References?

[Gdareos]

I've had problems with some users getting "Cannot find project or
library_ and I changed the Reference on my machine to look at
Microsoft Excel object library 8, as 11 was missing.

Loaded a module, and viewed code, then checked Tools->Reference.
Browsed for and found this:

[ ] Missing Excel Object Library, etc. Selected the reference, and saw
it wanted;

c:\program files\microsoft office\office\excel8.olb

When I selected this, it fixed the problem on my machine and a user's
when loading a particular application.

Nobody else was at work today (Saturday) so I couldn't check but
I'm a little worried, as I think some of the users expect to use:
c:\program files\microsoft office\office11\excel.exe

******************************************************
Question: Do all users of my Access '97 application have to look at
the same reference for Excel's object library?
******************************************************

If one has for example Excel 2000, would they be able to run the
application, or do I have to:

A) ensure all users have the same version of Excel
B) have a different copy of the application for each type of Excel
C See if there's a way to have the application figure out the type
of Excel library each has, and use the appropriate object library?

Is there an article that explains which Access 97 settings are global
and which are unique to a particular work station?

Thanks very much for any help this group has saved me several times
since I inherited this Access '97 application in March.
George

 

[Tony Toews [MVP]]

If one has for example Excel 2000, would they be able to run the
application, or do I have to:

A) ensure all users have the same version of Excel
Correct.

B) have a different copy of the application for each type of Excel

That's an ugly alternative and a PITA for you.

C See if there's a way to have the application figure out the type
of Excel library each has, and use the appropriate object library?

Yes, use late binding.

Late binding means you can safely remove the reference and only have
an error when the app executes lines of code in question. Rather than
erroring out while starting up the app and not allowing the users in
the app at all. Or when hitting a mid, left or trim function call.

This also is very useful when you don't know version of the external
application will reside on the target system. Or if your organization
is in the middle of moving from one version to another.

For more information including additional text and some detailed links
see the "Late Binding in Microsoft Access" page at
http://www.granite.ab.ca/access/latebinding.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Gdareos]

Thanks very much -- I just looked at the URL (and its many
references), and it looks as though this is exactly what I need. I'll
be sure to post the results and any bumps in the road, as I imagine
some poor soul will be in my situation.

I hate the idea of separate apps for different versions, as version
control would be a nightmare. BTW this app is a front end. All tables
are linked to.

I find my predecessor hard-coded quite a bit (his security is mostly
hard coded, so when users leave the company and new ones come in,
their usernames need to be added in at various points).

Thanks again,
George

 

[Tony Toews [MVP]]

Thanks very much -- I just looked at the URL (and its many
references), and it looks as though this is exactly what I need. I'll
be sure to post the results and any bumps in the road, as I imagine
some poor soul will be in my situation.

Please do. I don't mind clarifications or questions that I can use to
update my web page.

I hate the idea of separate apps for different versions, as version
control would be a nightmare. BTW this app is a front end. All tables
are linked to.
Absolutely.

I find my predecessor hard-coded quite a bit (his security is mostly
hard coded, so when users leave the company and new ones come in,
their usernames need to be added in at various points).

<sigh> Quick and dirty. You can, of course, replace those with a
table or two of permissions, etc, etc. Not very secure but ...

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/