Path: csiph.com!x330-a1.tempe.blueboxinc.net!feeder1.hal-mli.net!nx02.iad01.newshosting.com!newshosting.com!198.186.194.249.MISMATCH!transit3.readnews.com!news-out.readnews.com!postnews7.readnews.com!not-for-mail Date: Tue, 26 Apr 2011 19:54:33 -0400 Newsgroups: comp.lang.basic.visual.misc Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: Virtual Access Open Source http://www.virtual-access.org/ Organization: RDP Message-Id: Subject: Re: VB6 to Excel From: Steve Rindsberg Reply-To: steve@rdpslides.com References: Lines: 26 NNTP-Posting-Host: c424d059.news.iglou.com X-Trace: DXC=l]`o:Plg@A^iWd0f0h0laW?d1JL[FQ2iU_<:8iiJ9Z@_KZ:c?9jk:o]QRem6<;fd0Wm[6RgDcQ9?\ X-Complaints-To: abuse@iglou.com Xref: x330-a1.tempe.blueboxinc.net comp.lang.basic.visual.misc:114 In article , Gs wrote: > Steve Rindsberg presented the following explanation : > >> But as the others have already pointed out, there isn't much > >> difference between having a 'macro module' file you import into new > >> projects/workbooks or simply having a 'seed workbook/project', aka a > >> Template which already includes the macros you might want to use. > > > > I haven't done enough with Excel to say whether this'd be true as in > > some other Office products, but the ability to add code *via* code may > > be dependent on the user's security settings; they may not allow access > > to the visual basic project. > > Hi Steve, > The security settings are suppressed for automated instances. In this > case it might be possible regardless of user rights. As I already > stated, I've never written VBA programmatically but I've acted on the > VBE enough to know it's doable in an automated instance. Ah, thanks. That's good to know. I was fairly certain that there'd be no macro warnings in an automated instance but wasn't sure about access to the VBE.