No.

I got around it by digitally signing code and having my users add my to
their accepted digital signatures list.

It makes sense, if you could bypass it with code, there would be no macro
security!

"Edd" wrote in message
...
Hi Dale:

Were you ever able to sucessfully code the bypassing of this annoying
macro
security message?

Thanks,

Ed.


"Dale Fye" wrote:

Using Office 2003.

Yeah, I was hoping there was a way to do this programmatically.
Something
like:

Set xlObj = CreateObject("Excel.Application")
xlObj.MacroSecurity = 1
....
xlObj.MacroSecurity = 3
xlObj.close

Dale

"mr tom" <mr-tom at mr-tom.co.uk.(donotspam) wrote in message
...
Give this a try.

Open Excel.

Hit tools, options, security

Set macro secutiry to low.

Exit excel.

Hopefully this change will be picked up when you import into access.



"Dale Fye" wrote:

I've got an Access application that has to read some data (and perform
some
manipulation of it) from several Excel files.

Unfortunately, when I either import or link the Excel spreadsheets,
Access
is misinterpreting a field type and I am losing data. Because of
this, I
am
using automation to open Excel and read the records one row at a time,
doing
the appropriate data type conversions. Unfortunately, I keep getting
the
annoying macro security warning whenever I open the Excel files. Is
there a
way to bypass this warning and disable the Excel macros
programmatically?