I ran into this issue once before as well.  I'm guessing the problem has to do with 
using the Stream Server.  If your setup is like mine was, you have a Connect commmand 
like

Connect "C:\Program Files\Meditech\Workstation3.x\t.exe", stMeditech,"PathologyScript"

The help I got from Rich was that
 
"The Stream Server passes keystrokes through a 128 (not 100??) character buffer which 
clips any excess characters.  I'm afraid you'll have to break it up into 100 or so 
character separate key strings."

What I ended up doing was not using the Stream Server, and going back to

Connect "C:\Program Files\Meditech\Workstation3.x\t.exe", stMeditech

by removing the optional "PathologyScript" stream name argument. I have not had 
problems Keying large strings in after that.    This may work for you if you do not 
need to reference your stream by name.

Hope this helps,

Kevin Meagher
Analyst / Programmer
Mid-Columbia Medical Center - Information Systems
[EMAIL PROTECTED] 

>>> [EMAIL PROTECTED] 10/31/03 08:37AM >>>
I am working on a Meditech Magic Script that writes to a Pathology Results screen.  I 
have run into a problem where a string of text that I am reading from a text file and 
writing into the comment section will only wrtie 100 characters.  I've put a check 
into the code to see the actual length of the string and it contains over 400 
characters.  But when I "Key" the value in it stops at exactly 100 characters.  Has 
anyone come across this problem before and if so how do you get around it?
 
Linda Ralston, ISP 
Applications Analyst 
Peace Country Health 
Grande Prairie, AB 
Canada 

Reply via email to