|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
|May the source be with you, but remember the KISS principle ;-)|
|WSH||VBA Developer's Handbook||Office XP Development with VBA||Windows Registry|
|Excel VBA||MS Word VBA||PowerPoint||Etc|
VBA (Visual Basic for Applications) is the embedded programming language in the Microsoft Office suite of applications. VBA provides a complete integrated development environment (IDE) that allows for document automation, the process of using an automated template for creating documents. Word VBA Document Automation is for those advanced users who are looking to automate the task of preparing documents and programmers who are unfamiliar with document automation and the Word object model. Among the areas that need to be learned are:
There are few books on the subject of writing Word macros, and none of the available books on the market has complete coverage. Guy Hart-Davis's Word 2000 Developer's Handbook seems to be the best. Steven Roman's Writing Word Macros is not bad despite Amazon reviews (lemming effect ;-)
**** Microsoft Windows 2000 Scripting Guide
by The Microsoft Windows Resource KitAmazon.com Sales Rank: 3,031
Not for the faint of heart!, January 31, 2003
This book is massive!
Reviewer: A reader from TX United States
I will hand it to the reader from Indy that there are some typos, but every book I have seen that contains code has typos. Usually, this is attributed to the fact that the person(s) who edit the book, don't understand the material. Most coders are not good editors, and most editors are not good coders.
Putting that aside, I found this book to be an extremely valuable REFERENCE. I put that in caps because if you try to read it from cover to cover, you will wind up in a mental facility making little wicker baskets. That's probably what happened to the editors ;)
In addition to typos, these books frequently suffer from very bad indexes. The accompanying CD compensates for this shortcoming by providing a fully searchable electronic version of the book.
This book is a must-have, but it is not the scripting book to start with. If you are just starting, get Stanek's Windows 2000 Scripting Bible.
Managing Enterprise Systems with the Windows Script Host
Windows Shell Scripting and WSH Administrator's Guide
VBA Developer's Handbook, 2nd Edition
by Ken Getz, Mike Gilbert
A book for very patient beginners, September 21, 2001
On ocassions the author explains VBA for an specific application, say Word, but then he changes to give general explanations for all applications at once, disorderly mentioning exceptions for Excel, Word, Project or PowerPoint, what makes the reading difficult.
No, this book is not for me. I need principles and theory handsomely applied in concrete cases.
Many hype, tons of useless elements, total lack of structure, January 21, 2002
|After reading the book, the reader can answer
the question the author has: "why I wrote this book?". To glorify him obviously, since they're virtually everywhere
I-do-this, I-do-that, I-show-you-this-and-that. The reader knows perferctly that this book has been written by the
author (like any book!), so there's no need for this perpetual I-do-this things. Besides, the only element that
matters is not the author bur the book itself. If you can stand this self-promotion, then the worst is yet to come.
This book has no real structure, making its use and finding information a true headache. The summary is a clear proof: part 1) some essential background, 2)excel application development, 3) VBA, 4) userforms, 5) advanced techniques, 6) developing applications, 7) others. Since part 2 is devoted to devlopping, why this subject should again comes in part 6? Besides, isn't the whole book dedicated to developing? Finding what you want, even in the detailed contents, is harsh and shows that there's no plan, but rather disseaminated pieces of information, just like the VBA help.
Instead of clearly dividing by general topic (variables, objects, methods...), the author has a special order where everything seems mixed and spread in the book. Here something about methods, then some chapters later, another thing about methods etc.
And the author, instead of devolping and insiting on crucial themes, like accessing and working with external data (e.g. Access), contents itself with a short paragraph saying: please refer to other books! However, this book devotes around 100 pages to worthless history (starting with VisiCalc in 1978!!!) and the like. Incredible! That some historical material exist, why not. But that this comes while the essential is not here, that's inadmissible. That's why what this product is supposed to give begins only at page 120.
Besides, the layout (font, colors...) makes this book very unpleasant to read, so you want to close it ASAP, which is not exactly a good point.
The 3-star ranking reflects the amount of data provided, and some good points.
If you want a true and efficient book on Excel VBA, go for Definitve guide to Excel VBA which is really worthwhile.
Very light in content. Cannot do much after reading it, July 25, 2003
I have finished up to chapter 10. The contents are very light. It talks about very basic syntax that are almost the same in any language (e.g. C, Java, Perl C++...) It puts hundreds of pages that can be done in a half of the volumn. It does not tell you much about the object details. It seems to tell you to explore the objects and methods by recording macro and learning by trial and error. If so, I don't need this book.
First of all, time is money. I spent money, time to read hundreds of pages. The author suggests you to trial and error. I really don't think it is a very good book. But I still give 3 stars (I am quite geneous!)
Maybe most audiences of this book are never program in his/her life. This may be good for them. For someone who has experiences in programming. It is not very useful.
VBA For Dummies®
Better than fat VBA books, April 13, 1999
If you already know VB, this book is not for you, August 27, 2002
Anyone even a little familiar with using the VB language inside Word or Excel macros knows that the real study is how the internal application commands can be issued through the VB coding structure.
While Cummings knows a good deal about VB, he ultimately recommends that the reader use the Word and Excel help screens to learn how VB uses the application commands.
Unfortunately, a book about VBA needs to be about how to invoke these application commands from within the VB structure. Not going into these is like promising to teach how to cook a spaghetti dinner, and only explaining how to boil water.
If you don't already know VB, then pick up Wallace Wang's "Visual Basic 6 for Windows for Dummies". It gets half the VBA job done.
I'm still waiting for someone to write the other half.
Office XP Development with VBA
by Peter G. Aitken (Author)
Peter Aitken is the author of several interesting book on programming including:
Microsoft Outlook Programming, Jumpstart for Administrators, Developers, and Power Users
by Sue Mosher (Author)
Building Applications with Microsoft Outlook Version 2002 (With CD-ROM) in addition to Microsoft Outlook Programming,
Jumpstart for Administrators, Developers, and Power Users
|Reviewer: Kim Gorman from Cranford, NJ USA|
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes. If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner.
ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.
Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: September 12, 2017