Office 2003

  • Thread starter Thread starter scorpion53061
  • Start date Start date
S

scorpion53061

Has anyone done automation with Office 2003 with vb.net? How did it go(esp
Word, Excel, Access)?

Any problems I should be aware of? I am getting my copy next week so I
thought I should do some checking........
 
Thanks Herfried but I was looking for input from users who had experience
with using vb.net and Office 2003. I can read all I want what MS says but
usually from other developers I hear how it is actually going........
 
scorpion53061,
Have you tried asking "down the hall" in the
microsoft.public.vsnet.vstools.office newsgroup?

As I would expect every one using VB.NET & VS tools to have experience with
VB.NET & Office 2003.

Hope this helps
Jay

scorpion53061 said:
Thanks Herfried but I was looking for input from users who had experience
with using vb.net and Office 2003. I can read all I want what MS says but
usually from other developers I hear how it is actually going........
Click to expand...
 
You are right. It will help me make up my mind about whether or not to buy
it.
Up until you told me I was not aware such a product existed.

Jay B. Harlow said:
scorpion53061,
Have you tried asking "down the hall" in the
microsoft.public.vsnet.vstools.office newsgroup?

As I would expect every one using VB.NET & VS tools to have experience with
VB.NET & Office 2003.

Hope this helps
Jay
Click to expand...
 
* "scorpion53061 said:
Thanks Herfried but I was looking for input from users who had experience
with using vb.net and Office 2003. I can read all I want what MS says but
Click to expand...

I am sure there will be very few developers who have these experiences...
 
Visual Studio Tools for Office is pretty neat, but keep in mind that you
don't need it to automate Office 2003. VSTO lets you automate particular
documents -- it lets you write VB.Net/C# code that "runs behind" a document
(or document template.) E.g., a sales report document in Excel that
automatically downloads data from a server. Microsoft calls this a
"document-centric" perspective.

You can still use "classic" automation without VSTO -- either by developing
a COM add-in, or by automating an Office application using the Office object
model. I'm developing a COM add-in for Word with VB.Net, and there doesn't
seem to be any real difference between earlier versions of Word and Word
2003 in this regard.

Now if only I could customize Office 2003 to get rid of those hideous blue
menus and toolbars.... <g>
 
Back
Top