Sheri wrote:

> --- In [email protected], sgp
> <[EMAIL PROTECTED]> wrote: 
>> b. change the caption to include Acrobat.exe, for people who use
>> the full product instead of just the Reader
>> Wait.for(10000,activewindow("=AcroRd32,=Acrobat"))
> 
> Do you know it to work with full Acrobat?

I tested it with full Acrobat 8.1 and it worked, as far as I can tell.
I was able to type in a search term in CA text field, Rclick on the search 
button, see Acrobat open its 
search window with the search term I had typed, then Acrobat shows search 
results. If that's what it's 
supposed to do, then it's working with full Acrobat.

> Sometimes I think I should get the trial
> version of 8 just to see if they improved the Word add-in. But if my
> equipment is underpowered for version 7 with big docs with lots of
> cross referencing, I suspect it would be worse with 8.

I find 8's lighter than 7. Google for a second opinion.

> Anyway unless
> you've tested with full Acrobat, I'll stick with "=AcroRd32".

I have tested with full Acrobat 8. I haven't tested with Reader 8 :-)

> 
>> 
>> The above change works very well for me. Error trapping for when
>> wait.for expires without finding Acrobat is to be added to the
>> script.
> 
> Will definitely add a timeout and error trap.

Maybe you could spare the error trap by sending keys to the search window,
keys {to/toany c=whatever}...
this way if the search window doesn't show up before timeout expiration, no 
rogue keys are sent, and it 
all degrades to a no-operation - what else could it be since there ain't no 
search window to begin with?



Reply via email to