What is Office XP Developer?
WBM
I was wondering if somebody could give me some details about the developer
edition of Office XP. I could not find this info on MS Office XP Developer
web site.
Here my questions.
1. What is it compared to a regular Office XP?
2. How many CDs?
3. What is on thoses CDs. I'd appreciate some details please.
4. I understand it comes with Developer Editions of Exchange and SQL 2000.
What is the difference to the regular versions of those softwares.
5. What would one develop with Office Developer Edition?
Thanks in advance, and feel free to expand on anything else that would be of
interest to know about the developer edition.
WBM
Samuel Webster
http://www.microsoft.com/office/developer/suite/fastfacts.htm
| 1. What is it compared to a regular Office XP?
Office XP Professional. The complete Microsoft Office suite, including Word,
Excel, Outlook, PowerPoint, and Access.
FrontPage Version 2002. This new edition of Microsoft's Web development program
makes it easier than ever to create and manage Web sites.
Visual Basic for Applications (VBA). The version of Visual Basic designed
specifically for application development, VBA is ideal for building custom
applications that integrate Office XP and leading third-party, VBA-enabled
applications.
COM Add-in Designer. A powerful tool for extending the functionality of
applications, the COM Add-in Designer lets you write standardized dynamic-link
libraries (DLLs) that can be used inside any Office XP program.
Dashboard Project. Digital Dashboards provide access to both important
information and analytical tools in a single, easy-to-use desktop view.
Dashboard Project makes it easy to build the reusable Web Parts that go into
creating Digital Dashboards. It also provides templates for building complete
Digital Dashboards quickly.
Workflow Designer for SQL Server. Just one of the visual tools for defining
workflow processes included in Office XP Developer, the Workflow Designer for
SQL Server allows you to build Web-based business-process applications that use
SQL Server data. Solutions built with this tool can be taken offline without
sacrificing data integrity.
Workflow Designer for Exchange 2000 Server. Another visual tool for automating
business processes, Workflow Designer for Exchange 2000 Server focuses on
collaborative and tracking solutions that take advantage of all the features of
the latest version of Exchange Server.
SQL Server 2000 for Office XP Developer. This edition of SQL Server 2000 helps
you put your database-driven workflow application through rigorous testing
before you deploy it to your organization.
Exchange 2000 Server Developer Edition. A special version of Exchange 2000
designed to help you do thorough testing on collaborative applications before
you deploy them.
Visual SourceSafe and Visual SourceSafe Integration. Tight version control is
critical to a smooth development process. Features such as Check In/Out file
locking and visual differencing give you the tools you need to reconcile file
changes and prevent accidental code overwriting.
Code Librarian. A simple but powerful tool, Code Librarian brings new efficiency
to the development process by providing a comprehensive, searchable database
that makes it easy to manage and reuse code. Code Librarian also includes a
wealth of prewritten code sample and snippets.
Code Librarian Viewer. Even developers who don't have Code Librarian can take
advantage of code archived in a Code Librarian database with this freely
distributable viewer.
Royalty-Free Access Run-Time. This Office XP Developer licensing
agreement-including royalty-free distribution of Access version 2002
applications and Access Data Projects-makes it simple and extremely
cost-effective to deploy business applications.
Packaging Wizard. Launching solutions is easy with the Packaging Wizard included
in Office XP Developer. This tool identifies dependency files and creates
professional setup routines that can be distributed by way of any media,
including on disk, on a network, or on the Web.
Printed Developer Documentation. A print edition of the Microsoft Office XP
Developer's Guide provides all the important information you'll need to create
solutions with Office XP.
VBA Code Commenter and Error Handler. Code commenting and error handling can now
be done automatically with a single tool. VBA Code Commenter and Error Handler
provides customizable templates that add commented headers and automate the
creation of standardized error-handling code.
VBA Multi-Code Import/Export. Save time by moving multiple code modules in and
out of a project with a single operation.
VBA String Editor. This "what you see is what you get" (WYSIWIG) string editor
interface makes it easier to build strings for SQL statements and long scripts
written to be embedded in VBA code.
Microsoft Replication Manager. With Replication Manager, you can view, manage,
and synchronize Microsoft JET databases over a network or across the Internet.
| 2. How many CDs?
Does it matter?
| 3. What is on thoses CDs. I'd appreciate some details please.
The items listed above.
| 4. I understand it comes with Developer Editions of Exchange and SQL 2000.
| What is the difference to the regular versions of those softwares.
I think this is a licensing issue. You get sufficient licenses of these server
products to test a basic implementation.
| 5. What would one develop with Office Developer Edition?
Whatever software you think would benefit from having Office components as
programmable elements.
WBM
I'd still like to know on how many CDs it is supposed to come. I just
received it over our corporate licensing deal at work on 7 CDs, no book,
just the media and license. Office 2000 developer came on 11 CDs. Am I
missing some, or are there supposed to be 7 CDs?
I still don't know what one would develop with it though. Really, I'd think
database designers use SQL Server etc., but what can be developed with Word,
Excel, Powerpoint etc.? Can you give some examples please.
Thanks,
WBM
"Samuel Webster" <sam...@nospam4me.com> wrote in message
news:uWwvBAP8AHA.2268@tkmsftngp03...
Jim Stuart
able to distribute run time copies of Access 97.
I assume that Office 2000 and XP have retained this feature. Access is now
more tightly coupled to SQL server and if you have SQL Server in your office
environment you may find developer to be of use.
Jim Stuart
"WBM" <webm...@hotmail.com> wrote in message
news:upBV0tT8AHA.2280@tkmsftngp02...
Samuel Webster
| database designers use SQL Server etc., but what can be developed with Word,
| Excel, Powerpoint etc.? Can you give some examples please.
I think that is only limited by imagination.
Samuel Webster
If you REALLY can't think of anything, try asking on one of the 15+ Office
developer newsgroups. If you are programming something that can use all any or
all of the development compents yielded by web-enabled spreadsheet, charts, text
processor, graphics animation etc etc+
WBM
> all of the development compents yielded by web-enabled spreadsheet,
charts, text
> processor, graphics animation etc etc+
But do you need Office Developer for that?
The best reason for using Developer I have read so far is the ability to
create runtime Access databases.
I will check the newsgroups you mentioned. Having worked in corporate
environments for years now, I have never seen anybody using but the most
basic features of any Office application. I have never seen any custom
office application and am curious to find out about the possibilities
available.
As far as database environments go, usually I see SQL Server or Oracle with
either a VB or Web front end.
Maybe I am a little bit cynical, but it seems to me that what could be done
is mostly high tech fantasy, as opposed to what is going on in real life.
Even high tech companies do not really use any of the cool Office features
either because of security concerns, lack of training and also lack of
necessity.
Anyways, if you know of any custom applications in use, please let me know.
I do know digital dashboards, but again, haven't seen any company allowing
this in their network environments.
WBM
"Samuel Webster" <sam...@nospam4me.com> wrote in message
news:e6MBKrV8AHA.1380@tkmsftngp07...
Bobby
used - and I've *never* seen a genuine solution only based on Office
components (without complex VBA - and even that is rare). And as you write,
one of the biggest barriers is corporate IT - "You're not allowed to do
that", "We haven't installed that feature due to security concerns." etc.
"WBM" <webm...@hotmail.com> wrote in message
news:elHm5VX8AHA.1916@tkmsftngp04...
Samuel Webster
| is mostly high tech fantasy, as opposed to what is going on in real life.
I've seen really cool implementations of programmatic adaptations of Word and
Excel for document workflow in government and corporate sectors, plus management
reporting, SAP integration etc. I've seen a demo of wireless-enabled Excel,
Access and Outlook/Exchange used for managing fleets of boats. Excel is
especially used in the banking sector (and I've written some of that myself in
years gone by), plus I have friends who do custom applications in science and
engineering areas. Some of the Tech*Ed conferences I've been to have great
case-studies, but IMHO a lot more innovation in these areas goes on outside the
US which is very bureaucratic and throws a lot of manpower at menial clerical
work. Other countries have less resources and are more entrepreneurial about
using this technology.
| Even high tech companies do not really use any of the cool Office features
| either because of security concerns, lack of training and also lack of
| necessity.
If you still don't believe do a search of the web - a casual search this
morning found items like this http://www.beyondtechnology.com/profiles.shtml or
http://excelmagic.com/demo.htm plus a slew of programming houses who do custom
work in Office VBA. Don't forget MS sites like
http://msdn.microsoft.com/vstudio/centers/solution.asp or the Office developer
center. I think the new smart-tag technology is going to enable an interesting
class of corporate applications too.
WBM
As far as I can see it, the key is really Visual Basic, and not so much the
Developer Suite of software. It also seems to me, that most "custom" apps
are really embedded automation scripts (maybe with VBA) in regular versions
of Excel etc.
Would you agree that small to mid-sized companies are the main customers
here?
I will start a Visual Basic class next week and all this is very
interesting. Thanks again for you insight and the links.
WBM
"Samuel Webster" <sam...@nospam4me.com> wrote in message
news:e8uOlQc8AHA.2140@tkmsftngp05...
Samuel Webster
automate these very powerful objects. In addition you can write COM add-ins to
plug additional functionality into the applications. Basically you can
concentrate on the end-user solution without having to create your own basic
routines. I remember writing my own spreadsheet windowing code in DOS and
Windows years ago, and being very happy to throw it all out when object
libraries became available.
With Office development you have the choice of:
* having the objects in the background (although you need a licensed copy of the
relevant apps), and writing your own foreground interface
* using the objects as the foundation for a service
* masking the application interface and essentially providing a custom
application out of Excel (for example) that looks nothing like Excel
* allowing users to work in the application and call additional functionality
from your own code.
Internet Explorer has an object model that is similarly programmable.
As to the size of the companies using this, I don't believe there is any
restriction. Look into the small business Office and Server suites that
Microsoft sells which leverage the underlying rich objects. The sample links I
listed before had very large companies like Shell deploying this technology,
although not necessarily one solution across all employees or customers.
David R L Porter
from "Bobby" <bo...@europe.com> contains these words:
> Absolutely agree. In practice, only the most basic Office features are
> used - and I've *never* seen a genuine solution only based on Office
> components (without complex VBA - and even that is rare).
'
One area that Office could shine in is DTP. Although most print shops
dislike it, I am currently working with a UK university publishing
dept that actively solicits submissions laid out in Word. Many small
businesses use Word in this way and many more coul dif they thought about it.
Of course Microsoft has managed to spoil even this by the lack of an
effective crop-marking utility in Word (to position the page when
supplying Camera Ready Copy). The Knowledge Base kludges for Office
2000 are dreadful, and I'll bet XP doesn't solve the problem.
Hope somebody will prove me wrong, a kind ng contributor has already
confirmed to me that they've left the footnote bug uncorrrected.
--
Best wishes,
Bob Buckland ?:-)
You may want to check with the folks in the Word newsgroups
on news://msnews.microsoft.com and describe the footnote
problem you're experiencing.
FWIW, MS Publisher is the DTP featured app in the Office product
family. Word is text reflow, not page layout software.
In the 2002 series there is better capability for moving
a Word document into Publisher, but it does have room
for improvement <g>
===========
<<"David R L Porter" <david....@zetnet.co.uk> wrote in message news:200106121...@zetnet.co.uk...
One area that Office could shine in is DTP. Although most print shops
dislike it, I am currently working with a UK university publishing
dept that actively solicits submissions laid out in Word. Many small
businesses use Word in this way and many more coul dif they thought about it.
Of course Microsoft has managed to spoil even this by the lack of an
effective crop-marking utility in Word (to position the page when
supplying Camera Ready Copy). The Knowledge Base kludges for Office
2000 are dreadful, and I'll bet XP doesn't solve the problem.
Hope somebody will prove me wrong, a kind ng contributor has already
confirmed to me that they've left the footnote bug uncorrrected.
--
Best wishes,
David>>
--
Hope that helps,
Bob Buckland ?:-) MS Office/Word MVP
http://forums.compuserve.com/gvforums/default.asp?SRV=MSOfficeForum
*Courtesy is not expensive and can pay big dividends*
MS's Office XP - Information Trial Copy Order, Tour and more.
Office XP Main Page: http://microsoft.com/office/xp/
Office XP Tips Center: http://office.microsoft.com/assistance
Office XP Downloads: http://office.microsoft.com/downloads
Office XP Developers: http://msdn.microsoft.com/office/xp/
Office XP Deployment: http://microsoft.com/technet/office/xp/
Pick a MS newsgroup that matches your question topic:
via NewsReader:
http://support.microsoft.com/highlights/default.asp?pr=news&cl=179
via Browser:
http://communities.microsoft.com/newsgroups/default.asp?icp=prod_office
Office 2000 FAQs
http://support.microsoft.com/support/default.asp?SD=SO&PR=ofw2k
Office XP FAQs
http://support.microsoft.com/directory/content.asp?ID=FH;EN-US;offxp
Samuel Webster
| dislike it, I am currently working with a UK university publishing
| dept that actively solicits submissions laid out in Word. Many small
| businesses use Word in this way and many more coul dif they thought about it.
Microsoft Publisher is the Office family solution. Shoehorning Word into
becoming a complete DTP solution is not reasonable. It's probably not as bad as
the number of people who try to use Word as a database, but it's still not the
most appropriate way to sue the product. Yes Word could probably be extended in
this direction, but then you get half the world crying out at "feature
bloat"....
David R L Porter
from "Samuel Webster" <sam...@nospam4me.com> contains these words:
No, I don't think that's the point. Word is already a perfectly
adequate Camera Ready Copy origination program for DTP -- except that
it lacks the one feature that would make it completely usable (for
CRC) - crop marks. It isn't the world's hardest job to fix this, but
Microsoft has declined to do so just as they have - until XP -
consistently refused to include an on-screen word count (which I
remember appreciating in Psion's Xchange suite all those years and
years ago -- I was using Word 1.11 at the time AFIR and I used to
swap to Psion to do short articles because the on-screen count was so useful).
Word doesn't need to be shoe-horned into DTP viability. For several
versions we have been given DTP features (eg placing of images,
precise font measurements etc). I'm just asking for one more.
I have Publisher 2000 and have designed a couple of leaflets using it
but it doesn't have the same feeling of professionalism that Word
does and I can't see myself getting the results I get with Word
(charts, complex paragraph formats etc), so easily. And Publisher is
very unpopular with print houses - see the prepress newsgroup.
The footnote problem is just bad programming: you cannot in Word 95,
97, and 2K, rely on a footnote starting on the same page as it is
referenced in the text. Microsoft KB suggests manually forcing it to
do so etc but the problem should be properly addressed, not kludged.
A fraction of the programming time that went into that paperclip
thing would probably do it ....
Reminds me of the time (around Word 2.0) when I wrote to Microsoft UK
and offered to fix, for a reasonable fee, the fact that their UK
spellchecker accepted numerous US spellings. They said they already
had somebody in charge of spellcheckers. I pointed out that he/she
was their problem, not their solution, but they declined to reply ...