View Single Post
  #8   Report Post  
Posted to microsoft.public.excel.programming
Tom Ogilvy Tom Ogilvy is offline
external usenet poster
 
Posts: 27,285
Default Programmatically preventing macros issues

Then the original answer was appropriate.

--
Regards,
Tom Ogilvy


"Lew" wrote in message
...
Hi Tom:
VFP uses the excel com interface. I can grab an existence of the
excel.application object if one exists in the desktop environment or
create one if necessary, so I'm using the excel internals to get at the
data, not ADO (unless, of course, excel itself uses ADO to manage its own
data).
-Lew

"Tom Ogilvy" wrote in message
...
I guess that would mean you using ADO.

If your using ADO, then you don't start the excel application and you
should not get any prompts except for errors.

--
Regards,
Tom Ogilvy

"Lew" wrote in message
...
Guess I didn't say enough. The data is being pulled out by my VFP code
into corporate data stores. This allows us to have a single platform for
pulling from a large variety of sources ... (text, word, excel, ftp
stuff, etc...)
-Lew
"Tom Ogilvy" wrote in message
...
If you are using the clipboard and have a large amount of data, when
you attempt to close the file you could get a prompt to retain the
information in the clipboard.

You can suppress this with DisplayAlerts or you can copy an individual
cell to the clipboard before closing the workbook.

--
Regards,
Tom Ogilvy


"Lew" wrote in message
...
I'm writing an automation project which involves extracting data
from ss
we receive from a bewildering number of sources, and we're afraid of
the
possibility that my app may trigger a malicious macro. I understand
that
I've got to set the AutomationSecurity value to 3, but I've still got
a few
questions.
First: The tools-macros-security tab has 4 values; why can I only
set
the AutomationSecurity value to 1, 2 or 3 (ie only 3 possible values)?
Second: If I set AutomationSecurity to 3 and, since we plan to
disable
user interaction with excel while my app is running by making excel
invisible, is there any possibility that a macro (or anything else)
could
trigger a dialog requiring user input & resulting in an apparent hang?
If
yes, will DisplayAlerts = false take care of this? Please bear in mind
that
the only thing we're doing (as of now anyway) is pulling values out of
cells, not anything that I see as requiring interaction.
Other suggestions or things to watch out for?
TIA!



--
-Lew
The workers took the robot for Maria.