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