Pardon my newbie question

[Midnight Java Junkie]

Dear Colleagues:

I am looking for a way to customize our versions of office. In particular,
I would like to add a feature so that when somebody hits the print buttin, a
newly created dialogue box pops up with some type of indication as to what
printer they want to send their job to. You know, cute little pictures
telling them where their printers are physically located, breadcrumbs, etc.,
so that we dont have people sending fifty print jobs to a printer on the
other side of the world.

I am reading about the features in the developer's edition of office, but
when it comes to Office XP and Office 2003, for some reason I can't find a
developer's edition per se. Am I correct to assume that the XP and 2003
versions of office can have such things added to it by way of another .Net
type tool (we have all sorts of tools involving .net but I dont know what
they do).

In short, if somebody could give me a little quick overview of what
developing office through a kit actually means, the things that you can do,
cant do, etc., I would be mighty appreciative.

Thanks for your time,

Jolly Roger

 

[Howard Kaikow]

Office XP does have a Developer Edition.

Office 2003 has no Developer Edition.

You can use, say, VB 6 or VB .NET to automate Office XP and Office 2003.
And, you can purchase VSTO (Visual Studio Tools for Office) to make certain
types of automation easier, but the Office code is still VBA.

 

[Tony Toews]

I am looking for a way to customize our versions of office. In particular,
I would like to add a feature so that when somebody hits the print buttin, a
newly created dialogue box pops up with some type of indication as to what
printer they want to send their job to. You know, cute little pictures
telling them where their printers are physically located, breadcrumbs, etc.,
so that we dont have people sending fifty print jobs to a printer on the
other side of the world.

You can change the default printer using updates to the INI file and
some sample code.
See DefaultPRT.ZIP at http://www.mcwtech.com/downloads.htm. This MDB
has a combo box where you select the printer.

I am reading about the features in the developer's edition of office, but
when it comes to Office XP and Office 2003, for some reason I can't find a
developer's edition per se.

Such do exist but the names get changed.

Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm

In short, if somebody could give me a little quick overview of what
developing office through a kit actually means, the things that you can do,
cant do, etc., I would be mighty appreciative.

The most common reason for purchasing the developers edition is to
allow you to distribute a runtime version of Access along with your
app.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm