RE: IDDU linked files for S/36 flat files.

>Several businesses in town are looking at upgrading their S/36 to a 400
>(Where have we heard this before) The year/2000 has accelerated this. Has
>anybody else run into this problem with IDDU on CA/400? You actually "lose"
>flexibility when you go to the newer version of CA/400 in this environment.

-snip about how CA95 ignores IDDU and treats the file as a flat file-

Ouch!  One idea is to create the actual DDS'd file in another library and
copy the S36EE file to the DDS version and download that.  Weak but quick to
implement.  "All" you have to change is every PC transfer definition to
point to the new library.  Can you put a trigger on the S36EE file to keep
the DDS version updated "real time?"

Buck Calabro
Billing Concepts
+---
| 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
+---