Re: Word 2003 VB IDE & VB2005
- From: "Perry" <drumper@xxxxxxxxx>
- Date: Tue, 10 Apr 2007 01:23:01 +0200
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
.
- Follow-Ups:
- Re: Word 2003 VB IDE & VB2005
- From: CS Hayes
- Re: Word 2003 VB IDE & VB2005
- References:
- Re: Word 2003 VB IDE & VB2005
- From: Jay Freedman
- Re: Word 2003 VB IDE & VB2005
- From: Jonathan West
- Re: Word 2003 VB IDE & VB2005
- Prev by Date: Re: MID function no longer working in Word 2003 macro
- Next by Date: RE: Unprotecting Forms
- Previous by thread: Re: Word 2003 VB IDE & VB2005
- Next by thread: Re: Word 2003 VB IDE & VB2005
- Index(es):
Relevant Pages
|
Loading
