Excel8.olb

[Rick]

I am trying to export some data to Excel using the
Excel8.olb. I am finding that on some PC's an error
occures. I am sure it has to do with the version of Excel
they may or may not have, is there something simple I can
register on their PC's or include in the instalation that
would over come this? The errors that result are rather
odd, If the person does not have the proper version the
crash "blames" a query, If I remove the ref to Excel 8 the
problem goes away (Until they try to use the Excel 8
funtionality).

Thanks in advance, I am using Access 97, the users are on
98SE and XP PRO

Rick

[Cheryl Fischer]

> If I remove the ref to Excel 8 the
> problem goes away (Until they try to use the Excel 8
> funtionality).

Rick,

In your current environment, it appears that you will need to code for the
"lowest version" of Excel installed among your users. Here is a link to
MVP Tony Toews' page on Late Binding, which offers significant additional
information:

http://granite.ab.ca/access/latebinding.htm

--
Cheryl Fischer
Law/Sys Associates
Houston, TX

"Rick" <anon...@discussions.microsoft.com> wrote in message
news:090701c3d9d5$e91bcac0$a501...@phx.gbl...

[Rick]

I have been making alittle progress on my own on this and
based on your info it appearse I was on the right track,
But I am not exactly sure how I can solve this.

Most of the folks having the problem have Excel 2000 or
higher. THE PROBLEM is the database that is being used is
written in ACCESS 97 with Excel 97. Is there anyway I can
configure this WITHOUT convertinvg the DB to a higher
version of Access?? Do I have to put Excel 97 on the other
PC's? Is there an easy solution to this?

I will look at the link you gave me to se if it helps.

Thanks so much for the help!

Rick

>.
>

[Cheryl Fischer]

I'm fairly certain that Late Binding (and coding for the "lowest version" of
Excel) is the answer for your application.

I will say this, though... "mixed" environments, whether they be differing
versions of Windows, Office or other company-wide applications are expensive
to maintain and to work with, given the hours required to code work-arounds,
test and install tweaks, etc. In your "spare time", you might want to think
about and generate some numbers to show management some estimated cost
savings that could be achieved by software standardization.

--
Cheryl Fischer
Law/Sys Associates
Houston, TX

"Rick" <anon...@discussions.microsoft.com> wrote in message

news:000501c3d9e7$41430590$a101...@phx.gbl...

[Rick]

Thanks so much for your help. I love how you said "Spare
time" Been a while since I had that. Between work,
family, hobbies (which are supposed to be what we do for
fun right?? Mine is eating 30-40 hours of my week these
days! arg) I hardly know what spare time IS!!

Thanks again.
Rick
Ohio

>.
>