Hi Dave..........
Ok, I did everything you said, except the part about closing the Add-ins
didn't work too good, I got some kind of error message, so I just did Tools
Add-ins and un-checked them all.........then did all the other stuff and
still only get the #REF! in B1...........then I moved both the new files
over to the laptop, and they worked there fine again..............so, I
will check again tomorrow on the work computer and see how that
goes.........

Thanks again,
Vaya con Dios,
Chuck, CABGx3



"Dave Peterson" wrote in message
...
Well, this is a horse of a different color! (Or some statement of
surprise!)

Just some guesses...

If you start with a brand new workbook on the troublesome pc--close all
addins
and all other workbooks (just in case there's a name conflict
(instrrev97() or
pull()).

And put the code in that new workbook.
Then create a new workbook with something in A1 of sheet1.
Back to the workbook with the code.
type = in A1 of sheet1
point at sheet1 a1 of that other workbook

swap to the other workbook and close/save it.

Then put the equivalent of this in B1:
=pull("'C:\My Documents\excel\[book2.xls]Sheet1'!$A$1")

Ps. If you're gonna share the code with users of xl97, I'd just change
the code
to always use instrrev97--but you could code around it if you really
wanted.

pps. If you have addins loaded, you can close them by going into the VBE
and
hitting ctrl-g.

Then typing:
workbooks("myaddin.xla").close



CLR wrote:

Yeah, I hear ya RD.........I like it that way too.

Now, I got a really weird thing to report.
Last weekend I bought a 366 Celeron laptop for $15 at a yard sale. It
has
Win98SE on it with Office97 and only 32MB RAM. I just now copied the
PullMaster.xls and PullTest.xls I have been using here on my 1.2GHz AMD
Desktop with WinMe and Office97 and 2k and 512MB RAM (with which nothing
worked), over to the laptop. Once on the laptop and adjusting the
InStrRev
lines per Dave's 97function, the durn thing worked
perfectly!!!!!........go
figure.

So, this puts me in a quandry. I must go back to work tomorrow and try
on
that machine again, (Win98SE, Office97, 512MB RAM) the same protocol
I've
used here, thinking maybe I screwed something up Friday. If it works,
fine,
the problem boils down to my machine here at home and I can live with
that,
worry about it later. But if it dont work at work tomorrow, I have no
idea
to say why it works on some machines and not on
others.........strange.......could it possibly be a "setting"
somewhere?...........or a rights restriction?

Vaya con Dios,
Chuck, CABGx3

<<snipped