Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Tom Shelton Newsgroups: comp.lang.basic.visual.misc,microsoft.public.dotnet.languages.vb Subject: Re: Upgrading older VB programs (sans Project Files) to VB.NET Date: Fri, 13 Jan 2012 23:50:48 -0700 Organization: A noiseless patient Spider Lines: 22 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15"; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 14 Jan 2012 06:50:58 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="fRez9Qkc4tyPoJ3L2AFFmw"; logging-data="23830"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/yMY6Dv3uMgHghGT0sg+dhvmWVLTZ3RS0=" X-Newsreader: MesNews/1.08.03.00-gb Cancel-Lock: sha1:6akmRNbifqmmWOKWcm5Qh5F+XIE= X-ICQ: 543516788 Xref: x330-a1.tempe.blueboxinc.net comp.lang.basic.visual.misc:657 GS pretended : > Just want to interject that VB will persist to exist as the language > of choice for macros in MS Office. Since MS has reworked VBA to work > in x64 (VBA7), I don't expect VB to disappear in my working lifetime. > While it may be arguable that VBA is not Classic VB in various ways, > it remains that the underlying core to the VBA language IS Classic > VB! > > MS tried to take away VBA capability it Mac versions of MS Office and > got a horrific reaming for doing so. -Well.., at least enough of a > reaming that they put it back in pretty quick! > > I'm thinking there is not a dedicated special runtime for VBA, and so > unless I'm wrong MS will continue to ship that runtime with MS Office > if they take it out of Windows! Not where I work - we use VS tools for office. VBA is banned. -- Tom Shelton