MS Winword documents into long raw
From: <rt58_at_my-dejanews.com>
Date: Fri, 23 Oct 1998 12:42:07 GMT
Message-ID: <70ptj0$8g9$1_at_nnrp1.dejanews.com>
We are integrating 2 departments that have both Oracle 7 server. Department 1 (D1) has developed the applications by means of Developer 2000. Department 2 (D2) has developed the applications by means of Visual Basic and ODBC.
Now the two departments want exchange data and in particular MS Winword documents that
D1 has in LONG RAW columns handled by Dev2000. In order to test the D2 application that must re-use MS Winword documents we have:
- export table of D1 that contains MS Winword documents;
Date: Fri, 23 Oct 1998 12:42:07 GMT
Message-ID: <70ptj0$8g9$1_at_nnrp1.dejanews.com>
We are integrating 2 departments that have both Oracle 7 server. Department 1 (D1) has developed the applications by means of Developer 2000. Department 2 (D2) has developed the applications by means of Visual Basic and ODBC.
Now the two departments want exchange data and in particular MS Winword documents that
D1 has in LONG RAW columns handled by Dev2000. In order to test the D2 application that must re-use MS Winword documents we have:
- export table of D1 that contains MS Winword documents;
- import Table of D1 in DBMS D2
- read the long raw data through VB/ODBC application. In the future the two DBMS will be connected by sqlnet.
The file generated from the application, however, isn't recognized from MS
Winword.
What we have mistaken in this process?
Developer 2000 adds some byte of control, in the long raw column, in order to
know which client's application
has generated (and will handle) that object?
In this case, it's possible to eliminate these bytes?
There are data control for VB that handle correctly long raw column?
Every aid will be appreciated, thanks.
-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Fri Oct 23 1998 - 14:42:07 CEST