Word COM-application in a Citrix virtual environment

[Peter Karlström]

Hi

We have developed a COM-addin for Word 2007 which runs fine in an ordinary
"fat" client.
But when the application is used in a Citrix virtual client environment, we
get strange file-locks on the templates from which the documents are built.

If one logged in user creates a new document from a template, and another
user is opening another document based on the same template while the first
user have the document still open, the user which is trying to open a
document gets an error that the template is write-protected.

This does not happen when you do the same thing on an ordinary client.

The error occurs when we try to connect the opened document with the
template with the command docvar.AttachedTemplate = templatePath &
templateName, where docVar is a Word.Document variable, templatePath is the
path to the template and templateName is the template name, for instance
DocStandard.dotx.

What could be wrong?

Thanks in advance

[Jonathan West]

On several occasions I have found that VBA code behaves differently when the
template or add-in is open simultaneously in multiple instances of Word,
either in Citrix or of ordinary PCs where the templates have been placed on
a shared network folder.

The only slution i have found is a rigid insistance that a separate copy is
provided for each user (for Citrix) or PC (for local PCs).

On Citrix, it would go either in the profile or in a network drive to which
that user has exclusive access. For a local PC, it must go somewhere on the
local drive.
--
Regards
Jonathan West

Post by Peter Karlström
Hi
We have developed a COM-addin for Word 2007 which runs fine in an ordinary
"fat" client.
But when the application is used in a Citrix virtual client environment, we
get strange file-locks on the templates from which the documents are built.
If one logged in user creates a new document from a template, and another
user is opening another document based on the same template while the first
user have the document still open, the user which is trying to open a
document gets an error that the template is write-protected.
This does not happen when you do the same thing on an ordinary client.
The error occurs when we try to connect the opened document with the
template with the command docvar.AttachedTemplate = templatePath &
templateName, where docVar is a Word.Document variable, templatePath is the
path to the template and templateName is the template name, for instance
DocStandard.dotx.
What could be wrong?
Thanks in advance
--
Regards
Peter Karlström
Midrange AB, Sweden