R
rusty cranbrook
OWC is one of most poorly supported products ever issued by Microsoft.
Normally the community of developers gets enough support from MS at
some point to become self-sustaining. But with the OWC that has never
happened. Horrid documentation; intermittant and feeble support here
in the newsgroup by Microsoft; and the OWC is anything but self
evident.
I have posted so many questions here about the OWC. Almost none have
been responded to. The rare replies are exclusivly from fellow
developers; nothing from Microsoft. Microsoft, since Office is your
cash cow, it behooves you to free up a bit of funding for a person or
two to learn the OWC and help the community get up to speed. I do not
feel very good about spending my money on Office developer products
when the only dev tool that Microsoft really supports is .Net. .Net is
fine and dandy but some of us out here are still trying to work with
Office.
Normally the community of developers gets enough support from MS at
some point to become self-sustaining. But with the OWC that has never
happened. Horrid documentation; intermittant and feeble support here
in the newsgroup by Microsoft; and the OWC is anything but self
evident.
I have posted so many questions here about the OWC. Almost none have
been responded to. The rare replies are exclusivly from fellow
developers; nothing from Microsoft. Microsoft, since Office is your
cash cow, it behooves you to free up a bit of funding for a person or
two to learn the OWC and help the community get up to speed. I do not
feel very good about spending my money on Office developer products
when the only dev tool that Microsoft really supports is .Net. .Net is
fine and dandy but some of us out here are still trying to work with
Office.