Hi!

We have a VFP service running on the server machine and printing documents from the Word in automated mode. When someone tried to work with the Word at the same time, there are no conflicts and hangs up - we managed to make this with so big effort, that you even cannot imagine. With Citrix user will not be able to kill the Word if you get it show dialog box or hang up because some other reason. Just because there could be a lot of other Words opened by other users so you will easy get lost which Word is yours. There is also a memory issue.

If you use the Word just to create and print the document, better make the Word management service. This service will get user requests and process them one by one by allowing is disallowing to run the Word. So, only one Word instance will be opened for all users.

HTH.

>Hi there,
>
>In one of our software packages we use word automation to generate neat RTF reports. This apeared to be preferable over the native foxpro reports, because of the ability to edit/save and mail the reports.
>However, some of our clients use a terminal server/cytrix environment and stange things happen over there.....
>The terminal hangs and needs to be reset after an attempt to incorporate word as object into the program.
>Most of the time we don't get an error message at all, but very rarely we get the message "De opslagruimte vo", which is a dutch message and can be translated as "The storage capacity for". Obviously, most of the error message is lost as windows only shows the first part of the error message.
>Here, at our developers' office we do not have/use citrix or windows terminal server so it's pretty hard to debug this problem.
>I wonder: does the program attempt to open word as installed on the client or word as installed (if at all) on the server? If the latter, I can imagine we have a problem. Is there a way to convince terminal server/Cytrix to adress the LOCAL installed word when it encounters the famous command "oWord = CreateObject('Word.Application')"? What is the reason the server-side resident Word can't be adressed? Does anybody have any experience/ideas/solutions to our problem?
>
>
>oMessage = CreateObject('With_Kind.Regards')
>
>Geert van Snik
>Zorgned Automatisering
>Wageningen, the Netherlands