Office Vision Date problem

["Mike Cunningham" <MCUNNING@xxxxxxx>]

We just discovered that an Office Vision document can not deal with a field 
defined as 8.0 and contains a date in a merge operation.  This field use to be 
a 6.0 field and contained a date (i.e. 052799) and using the date editing in OV 
printed as 05/27/99.  Now this is an 8.0 field and contains a date (i.e. 
05271999) and the same date editing in OV printed as 27/19/99.  Only the last 6 
positions of the 8.0 field were used.  A call to IBM support agreed that this 
is a problem and there are no plans to fix it since OV is being phased out.

Has anyone figured out a way around this ?

On a related question, has anyone found a replacement for the PRTDOC command 
when OV goes away ?

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---