Re: Word 2003 VB IDE & VB2005

I'm trying a trial of Office 2007 and the VBA ide is VB 6.5
am I missing something here?
Nope, correctomundo

If MS is migrating to VB.NET then why the
release of 2007 with VB 6.5?
Only InfoPath 2007 ships with VB.net IDE.
I hope VB.net IDE will ship with SR1 or SR2 of Office 2007.
I've noticed some apprehension among VBA expert colleagues here in Holland.
I'm trying to convince them into investing in VB.net. My message is finally getting through to
them but only after having showed them apps I developed and demonstrating the richness of the IDE.

From what I understand (and it's not a lot) VB.NET or VS2005 are external
from Office and VB 6.5 is internal or attached directly to the individual
program (i.e. Word, Excel, Access etc.)
Strike!

I also, apparently, grasp that it is safe to learn VB 6.5 for Office
as a tool for creating small solutions for clients (is this true?)
True.
But, think about:
Ok, as a beginner you would need to invest in VBA 6.5 all the same, right?
Why not use the effort to learn VB.net from scratch, I wonder?
As a beginner, it will take some effort (courses, courses and courses) but if you have some affinity with programming
and your MS Word knowledge (I mean power user knowledge and not programming knowledge) is good, why not skip the VBA 6.5 step
and jump right into VB.net?
How is your MS Word knowledge by the way?

--
Krgrds,
Perry

System:
Vista/Office Ultimate
VS2005/VSTO2005 SE



"CS Hayes" <hayes.cs(remove this)@gmail.com> schreef in bericht news:312DDE15-6587-4126-B65B-E7B91A12A463@xxxxxxxxxxxxxxxx
I've been feeling my way around this issue. I really don't know what is
what. What provoked this question was the fact that (out of curiousity) I
looked at what version of VB the Office Suite was using (via [help], [about].)
I'm trying a trial of Office 2007 and the VBA ide is VB 6.5
am I missing something here? If MS is migrating to VB.NET then why the
release of 2007 with VB 6.5?
From what I understand (and it's not a lot) VB.NET or VS2005 are external
from Office and VB 6.5 is internal or attached directly to the individual
program (i.e. Word, Excel, Access etc.) I also, apparently, grasp that it is
safe to learn VB 6.5 for Office as a tool for creating small solutions for
clients (is this true?)
Can I obtain literature (books, training) on using the VB 6.5 and progress
in that direction or is it an area that is not covered? (I'm really not sure
what books to get, I just ordered "Visual Basic 2005 Step by Step" but that
wouldn't help if I was focusing on the VB 6.5)
--
Chris Hayes
Still a beginner (only 12 years)


"Perry" wrote:

Hi CS Hayes,

Let me bring my 20-cents-worth to the table :-)

Interesting topic.

Because of business dependency on legacy VB(A) applications/projects, MS
can't stop full support of that platform.
And there are a lot of VB(A) projects out there... ;-)
I agree.

But, old man, I think you're right. It is the way to go ...

Here come the 20 cents:

(VB2005, read VB2 005.NET and/or VSTO 2005 SE)

VB2005 vs VB6
I use VB6 only for support to legacy VB6 apps.
I've moved to VB2005 completely for new apps.

VB2005 vs MS Access VBA
MS Access is famous for RAD when it comes to database app development.
With VB2005 (and ADO.net), turn around times regarding delivery of database
app development are (or can be) equivalent.
The VB2005 IDE is ... ahem ... richer, though. (apart from the MS Access
Main/Subform functionality)
What do I favour? Sometimes MS Access, but more and more: VB2005.
Personally, I'd say: 70% VB2005 and 30% Access

VB2005 vs MS Excel VBA
The MS Excel legacy VBA power is humongeous. So no favour when it comes to
delivering Excel development projects.
VB2005 vs Excel: 50/50 with a slight favour to VB2005 because of the
richness of the windows forms in VB2005.
I'm waiting for the Office 2007 fully supported PIA's for Excel. This could
turn things around in favour of VB2005.

VB2005 and MS Word VBA
MS Word development in an enterprise setting: rapid document production
tooling.
There's practically no other (enterprise) interest to MS Word besides:
Getting my data as fast as possible into (presentable) enterprise documents
with the least of efforts.
Because of the hidden binary document specifications of MS Word (in all MS
Word versions prior to 2007), y'd always need
the MS Word application to create documents. So, programming MS Word using
an automation client or using MS Word VBA didn't make
any difference to me.
So before Office 2007, the VB2005 vs MS Word VBA would score: 50/50 as well.
With Office 2007 however and XML being the MS Word document foundation, this
will change.
If you know the internal directory build up of MS Word documents, and the
XML specifications of the dependant XML files to go with it, you can
create MS Word documents using ... notepad.
In case you didn't know: change the .docx or .docm file extensions of MS
Word 2007 documents into .zip and open this renamed file in Windows Explorer
and explore ...
This will change MS Word document production tremendously from a developer's
point of view, once expertise around this subject grows in the development
community.
Like with Excel, I'm waiting for the full Office 2007 interop wrappers to
come available.
Until then, the score for VB2005 vs MS Word 2007 would read: 50/50 but will
change in favour of VB2005.

Hope this was usefull to you
:-)

--
Krgrds,
Perry

System:
Vista/Office Ultimate
VS2005/VSTO2005 SE



"old man" <oldman@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:E2D7B19A-B283-44BB-9D8E-2138E57EA2ED@xxxxxxxxxxxxxxxx
> Hi,
>
> I don't like disagreeing with a Word MVP but you may be doing the
> equivalent
> of building a great horseshoe just when cars are being widely > introduced.
>
> Microsoft is very commited to .Net and VSTO and finally the development
> environment for Word is as good as the one for Excel (the Word one was
> always
> 1-5 years behind). The Office Object model still reflects a long > product
> history (so it is rather unusual) but it is much better and if you want > to
> develop software for the long (sic) run use VSTO and .Net. Its much > harder
> for VBA programmers to get but it is truly object oriented and you get
> access
> to the CLR and the .Net libraries.
>
> This is a very emotional issue for users who have learned and pushed > VBA
> to
> places no one ever anticipated but VSTO is the way to go. I don't want > to
> start a flame war and I have the greatest respect for the VBA experts > on
> this
> site but that is the way it is.
>
> old man
>
> "Jonathan West" wrote:
>
>>
>> "CS Hayes" <hayes.cs(remove this)@gmail.com> wrote in message
>> news:96EA87CD-B81F-4DCB-9F3A-2DACCBB84443@xxxxxxxxxxxxxxxx
>> > So, here's another question:
>> >
>> > If I was interested in developing small solutions with Office >> > products,
>> > what
>> > side should I focus on?
>>
>> I would recommend you stick to VBA unless you already have a >> substantial
>> VB.NET application to which you want to add some capability to >> automate
>> Office.
>>
>> VBA is tightly integrated into the office apps. You can get much >> better
>> context-sensitive help for the office object models, and you can run >> the
>> macro recorder and get some sample code -a kind of "code-by-example". >> Of
>> course, you willusually need to refine the recorded code but even
>> experienced programmers sometimes find it useful to see what objects >> are
>> used for a particular purpose.
>>
>>
>> -- >> Regards
>> Jonathan West - Word MVP
>> www.intelligentdocuments.co.uk
>> Please reply to the newsgroup
>>
>>
>>


.

Relevant Pages

  • Re: Learning VBA
    ... Another way would be to paste the code into a Word document and save the module as text only, then import the module back into Excel. ... I'm a bit surprised that your VBA buddy didn't try this, but give it a shot and see what happens. ... whatever programming language becomes the default that the Mac and PC ... I don't want to discourage you from getting started on programming. ...
    (microsoft.public.mac.office.excel)
  • Re: VBA errors in 2007 (works fine in 2003)
    ... It's just breaking on the Mac version of Excel. ... Pak allowing you to call functions in the ATP from within VBA. ... menu in VBA, choose References, and select "atpvbaen.xls". ... If there is the possibility of a name collision (two or more libraries ...
    (microsoft.public.excel.misc)
  • Re: Excel: ADDRESS cannot be used in CELL. How stupid is this?
    ... to keep Excel from crashing when I use the evalaute formula ... use VBA to manipulate data with Word/Access ... How lame is the 'talent' programming Excel? ...
    (microsoft.public.excel.worksheet.functions)
  • Re: VBA errors in 2007 (works fine in 2003)
    ... The file is working as intended now in Excel 2003 and 2007. ... Pak allowing you to call functions in the ATP from within VBA. ... menu in VBA, choose References, and select "atpvbaen.xls". ... If there is the possibility of a name collision (two or more libraries ...
    (microsoft.public.excel.misc)
  • Re: macro advice
    ... You can access VBA by pressing Alt F11. ... Excel 2002 VBA Programmers Reference; John Green, Stephen Bullen, Rob Bovey, ... Excel 2000 Programming For Dummies; John Walkenbach; 408 pages; Hungry ... lists VBA code on his website that solves various challenges. ...
    (microsoft.public.excel)
Loading