Re: References for VBA

But the code I used was in the Help for both Access and Word. In Word it
just worked, whereas in Access I had to check various references until I
could make it work. In neither place did it mention that any references
were needed. That's the point...I got the code out of the Help files for
Word and I saw the identical code in the Help files in Access, but in
neither place did it mention that the functionality wouldn't just work "out
of the box." If it isn't Microsoft's responsibility to document what you
need to do to make the code in their own help files work, then whose is it?
Are developers supposed to just GUESS, like I did? That seems to be a bit
of an odd attitude for a company the size of Microsoft to take for their
products.

-Amy

"Jonathan West" <jwest@xxxxxxxx> wrote in message
news:umy8cjM0FHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
>
> "Amy Blankenship" <Amy_nospam@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:ef3X2dC0FHA.464@xxxxxxxxxxxxxxxxxxxxxxx
>> That's not so much what I meant (sorry for the delay...been out of town).
>> If you try some code in VBA from within whatever application and it
>> doesn't work, how do I know what references to check to MAKE it work,
>> since the help files never say "this functionality only works if you
>> reference blah blah"
>
>
> That is usually because the object you are using is not within the object
> model for that application. Its a bit hard for Microsoft to document
> everything that isn't there as well as everything that is!
>
>
> --
> Regards
> Jonathan West - Word MVP
> www.intelligentdocuments.co.uk
> Please reply to the newsgroup
> Keep your VBA code safe, sign the ClassicVB petition www.classicvb.org


.