Answering dialog boxes

[David Wheeler]

Hi,

Part of the macros I'm writing involves opening a file, copying data
from it, closing the file and pasting the data elsewhere. When I do
{FileClose 0} I get a dialog asking whether I should keep the data on
the clipboard. I always want to answer Yes. Is there a way to get the
macro to answer this dialog?

cheers,
David

[lemoto]

David:

A tilde ~ represents Enter and might do it.
Better is not to Copy and Paste but {BlockCopy...} or {BlockValues...},
which do not use the clipboard. If the destination is not QP, of course
this is no use.
--
Good wishes!
Roy Lewis
C_Tech volunteer
(UK)

[Mark Strzyzewski]

A long time ago in a galaxy far far away...the programmers for QP decided
that anything copied to the clipboard over a certain size should prompt a
warning message if you close the file. The solution you seek depends on
when you are pasting the data elsewhere.

If the paste is done within Quattro Pro and you do the paste first then
close the file, copy something else to the clipboard before closing the
file. That way, something small is on the clipboard. This is the method I
usually use. Instead of just {Fileclose 0}, use:
{SelectBlock A:A1}
{EditCopy}
{FileClose 0}

If the paste is done in another application, and you need to paste the data
after QP is closed, then you may have to live with it. Currently, there is
no way to suppress the clipboard dialog box.

If the paste is done in another application, another way to do it might be
to have QP take control of the other application through DDE to do the
paste, and then use my first solution to close the file. Unfortunately, I
have zero experience with doing this.

--
Mark Strzyzewski
C_Tech Volunteer - WP Office Suite
For the benefit of all, please keep the discussion to the newsgroup.
PSA: Please Do not attach files to postings in these newsgroups.

[David Wheeler]

lemoto wrote:

> Better is not to Copy and Paste but {BlockCopy...} or {BlockValues...},
> which do not use the clipboard. If the destination is not QP, of course
> this is no use.

OK I've got it to work using BlockValues. Onto the next problem.