Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!nx01.iad01.newshosting.com!newshosting.com!198.186.194.250.MISMATCH!news-xxxfer.readnews.com!news-out.readnews.com!postnews7.readnews.com!not-for-mail Date: Mon, 25 Apr 2011 15:57:35 -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: 14 NNTP-Posting-Host: fb5fe820.news.iglou.com X-Trace: DXC=;C>TP<2;?36fe>HaoCKRX>?d1JL[FQ2i5nZ@RbAjodQ6KZ:c?9jk:o=QRem6<;fd07=Z:aZcZ:D`0 X-Complaints-To: abuse@iglou.com Xref: x330-a1.tempe.blueboxinc.net comp.lang.basic.visual.misc:108 > 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.