G
G. Tarazi
Well, I am used to complain about InfoPath in this newsgroup so why not
about office, since InfoPath is involved in what I am trying to do too this
time.
Anyway, there is a commercial on TV, about happy employees cheering and
jumping around, just because they've done their project successfully using
Microsoft Office, but in real live thinks are different
So, have you ever tried to use the Word Object module from InfoPath using an
InfoPath project and C# .net?
A simple task, of passing the contents of 2 rich text boxes from InfoPath to
word and trying to get the differences between them back to InfoPath seams
almost impossible.
I know, 10 lines of code in Microsoft Word (theoretically), but only if you
can understand they super, super, super stupid object module that word uses
(that was ported to C#) (don't believe it's super stupidity?, create your
first Microsoft Word project and try it your self)
And that is the first week of trying to achieve that with no luck.
I just don't understand, in the commercials about office, everyone talk
about how integrated this product is, and when you try to develop something
with it, you realize that you are working with a group of unrelated products
packaged in one package called "Office".
So, if I can't link 2 products to gather to achieve the task, where is the
integration?
You can't even set the value of a rich text box in InfoPath directly without
losing the formatting, or you should use 2 DOMs to keep the formatting; it
is like selling someone a car and convincing him to use the trunk to get in
to his car, sine the doors are designed to open from inside out only
Assigning a control with a value is the simplest thing you can ask from a
product, and that is not simple in InfoPath, so you can imagine of porting
this value to another Microsoft office product.
Not mentioning the security exceptions, the problems debugging an InfoPath
form that is trying to connect to a word because of these exceptions, and
then you must sign the form, and it will become harder to debug, etc.
Tons of problems to achieve a simple thing.
And again, do less with more! Microsoft!
Can't you just stop lying for once? The first biggest lay I heard last year
was BizTalk 2004 and it was dumped, and I am not planning to use it until
2010, the second biggest lay is office integration for developers.
Thank you for lying to us.
about office, since InfoPath is involved in what I am trying to do too this
time.
Anyway, there is a commercial on TV, about happy employees cheering and
jumping around, just because they've done their project successfully using
Microsoft Office, but in real live thinks are different
So, have you ever tried to use the Word Object module from InfoPath using an
InfoPath project and C# .net?
A simple task, of passing the contents of 2 rich text boxes from InfoPath to
word and trying to get the differences between them back to InfoPath seams
almost impossible.
I know, 10 lines of code in Microsoft Word (theoretically), but only if you
can understand they super, super, super stupid object module that word uses
(that was ported to C#) (don't believe it's super stupidity?, create your
first Microsoft Word project and try it your self)
And that is the first week of trying to achieve that with no luck.
I just don't understand, in the commercials about office, everyone talk
about how integrated this product is, and when you try to develop something
with it, you realize that you are working with a group of unrelated products
packaged in one package called "Office".
So, if I can't link 2 products to gather to achieve the task, where is the
integration?
You can't even set the value of a rich text box in InfoPath directly without
losing the formatting, or you should use 2 DOMs to keep the formatting; it
is like selling someone a car and convincing him to use the trunk to get in
to his car, sine the doors are designed to open from inside out only
Assigning a control with a value is the simplest thing you can ask from a
product, and that is not simple in InfoPath, so you can imagine of porting
this value to another Microsoft office product.
Not mentioning the security exceptions, the problems debugging an InfoPath
form that is trying to connect to a word because of these exceptions, and
then you must sign the form, and it will become harder to debug, etc.
Tons of problems to achieve a simple thing.
And again, do less with more! Microsoft!
Can't you just stop lying for once? The first biggest lay I heard last year
was BizTalk 2004 and it was dumped, and I am not planning to use it until
2010, the second biggest lay is office integration for developers.
Thank you for lying to us.