pnp

Hi all

I have a somehow weird problem. We have implemented at Word VSTO Solution. In this word document we use a lot of XML tags to locate data and be able to extract it from the document, and save the document as XML and send this to a reporting tool.

All this works as expected. The problem appears when a person from our company HQ sends the Word document to one of our subsidiaries. The subsidiary has not yet the VSTO code rolled out, so when the document is opened there it's just a normal Word document. The subsidiary fills out the fields, mails the document back to us, and once the document is opened here, all the XML tags are missing ! All the text in the document is "as-should-be", but the surrounding tags are gone, and hence the VSTO code have a very hard time working with the document.

Both sides use XP SP2, and Office 2003.

Has anybody experienced this before, or is anyone able to figure out why this might happen

I can't see any reason to why Word should remove these tags.

I hope somebody can point out what we do wrong.

Best regards

Anders



Re: Visual Studio Tools for Office XML Tags in VSTO documents disappear

Cindy Meister

Hi Anders

could you have the subsidiaries check whether their Office 2003 is the PROFESSIONAL or the STANDARD edition Only the Pro edition supports XML tags.






Re: Visual Studio Tools for Office XML Tags in VSTO documents disappear

pnp

It should be professional - so they claim... :-)

/Anders




Re: Visual Studio Tools for Office XML Tags in VSTO documents disappear

Cindy Meister

<< The subsidiary has not yet the VSTO code rolled out, so when the document is opened there it's just a normal Word document. The subsidiary fills out the fields, mails the document back to us, and once the document is opened here, all the XML tags are missing ! All the text in the document is "as-should-be", but the surrounding tags are gone, and hence the VSTO code have a very hard time working with the document.>>

pnp wrote:
It should be professional - so they claim... :-)

OK, in that case the next thing I'd check is what file format they're saving to. Possibly they've set the default (Tools/Options/Save) to something older file format that doesn't support XML tags.

If that's not it, the next thing would be to "look over their shoulders" as they work. Is it possible that they're selecting the XML tags and deleting them without realizing it Is the related XML schema installed on these machines so that they can view the XML tags in the document as they work (display the XML structure task pane)






Re: Visual Studio Tools for Office XML Tags in VSTO documents disappear

pnp

That was some of my initial doubts as well... That the error occurred by the users doing something bad without knowing it.

I have made a 4 step guide, where they in between each step does ctrl+shift+x to verify if the xml tags are still there. That might spot something.

I would not believe the xml schema is installed on their machines. For users in our building this is done by the VSTO code, and since they don't have the code, and no one has thought of doing it manually - i will not expect them to have the schema installed.

Could this cause this That if word does not have the schema installed, then it will remove the tags Will it make them unable to view the tags, if the schema is not present

/Anders




Re: Visual Studio Tools for Office XML Tags in VSTO documents disappear

Cindy Meister

Hi Anders

OK, I made a quick test and they should be able to see the tags (assuming they have Office Pro). But it's possible the tags aren't displayed - that's a setting that may need to be activated (in the XML Structure task pane).

The only other trouble-shooting step that occurs to me is to try setting up a document with XML tags in Word (not as a VSTO project) in a similar manner. See if the same problem occurs. And set up a machine for testing without the VSTO solution, open the VSTO document and see what happens.






Re: Visual Studio Tools for Office XML Tags in VSTO documents disappear

pnp

I have tried opening the document where the VSTO solution was not available - or at least the solution did not have full trust, so it could not execute - that didn't cause this behaviour.

As I mentioned before, my suspicion is that the users at the subsidiary does something that causes them to somehow delete the tags. My first thought was that they might have an old version of the document (without xml tags) prefilled with some common values, and then they might copy-paste this old document on top on the new - which clearly would make the xml tags disappear. To an ordinary Word user this would seem like a harmless act, but it could be causing this.

We have sent some tasks they should perform, and report back with the results. Due to time zones etc, I will probably not having answers before tomorrow.

When I know more I will of course post the result.

Thanks for suggestions so far.
/Anders




Re: Visual Studio Tools for Office XML Tags in VSTO documents disappear

pnp

Hi again

Well... We thought we had found it... After asking the subsidiaries again, one of the people there answered that he had two laptops, one of them with only Office Std. But after having tested it, it actually seems as if Word Std leaves the xml tags intact in the document, it just won't use them. So no solution there.

After been doing some testing on the workflow for all the people involved, and nothing seems to be able to explain this behaviour I tend more and more to a failure in one of the most critical components... Human communication... ;-)

I have not been directly involved in tracking this issue until now, and there might have been some failure in communications, so that the subsidiaries might have been using an old template or something similar...

Anyway, thanks for taking your time to help me figuring some testing scenarios out, one of them almost payed off. I will keep tracking the issue, and if anything new comes up I will post it here.

Hopefully the effort done now, has ensured that all people involved are working on the latest version of the document, and thus the problem might have been solved like that.

Best regards

Anders