creating dBASE files from OI (OpenInsight 32-Bit) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
{{tag>category:"OpenInsight 32-Bit" author:"Mike O'Neal" author:"Warren Auyong" author:"Ray Chan" author:"Richard Hunt" author:"Karen Oland"}}

[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]


==== creating dBASE files from OI (OpenInsight 32-Bit) ====
=== At 29 JUL 2008 11:17:09PM Mike O'Neal wrote: ===
 
 
<QUOTE>
Hi all - 



Is there a way to create dBASE files from OI?



TIA,



Mike O.
</QUOTE>
----

=== At 30 JUL 2008 01:12AM Warren Auyong wrote:  ===

<QUOTE>See this thread



http://www.revelation.com/o4wtrs/oecgi3.exe/O4W_DOMINO_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&KEY=793A7E27A9EFA665852572ED006110A3&KEY1=793A7E27A9EFA665852572ED006110A3

</QUOTE>

----

=== At 30 JUL 2008 01:35PM Mike O'Neal wrote:  ===

<QUOTE>Thanks Warren, but I need *export* into a DBASE file, not *import* a DBASE file.



Mike O. 

</QUOTE>

----

=== At 30 JUL 2008 01:48PM Warren Auyong wrote:  ===

<QUOTE>You can read and write using ADODB. You can even create tables.



http://msdn.microsoft.com/en-us/library/ms677516%28VS.85%29.aspx

</QUOTE>

----

=== At 30 JUL 2008 01:56PM Warren Auyong wrote:  ===

<QUOTE>Here's some sample code on how to create a table and populate it in VB via ADODB. VB is easy enough to translate into BASIC+. Substitute the DBASE connection string for the Access connection string:



http://www.vb-helper.com/howto_ado_create_table.html

</QUOTE>

----

=== At 30 JUL 2008 02:14PM Warren Auyong wrote:  ===

<QUOTE>For DBase III files use the following connection string:



    "Provider=Microsoft.Jet.OLEDB.4.0; Data Source=D:\My Documents\dBase;Extended Properties=dBase III;" 



Substitute in the appropriate path.

</QUOTE>

----

=== At 31 JUL 2008 01:12PM Mike O'Neal wrote:  ===

<QUOTE>Wow!  Thanks Warren!  I will sort through all of this and give it a try.



Regards,



Mike O.

</QUOTE>

----

=== At 31 JUL 2008 02:02PM Ray Chan wrote:  ===

<QUOTE>Just curious, but why are you exporting data from OI to dBase?



I didn't know that DBase was still around.



Ray Chan



</QUOTE>

----

=== At 31 JUL 2008 10:02PM Richard Hunt wrote:  ===

<QUOTE>And how about multivalue fields? dBASE does not support multivalue fields.

</QUOTE>

----

=== At 01 AUG 2008 12:55PM Karen Oland wrote:  ===

<QUOTE>You have to create child tables. Way back in AREV days, we had an export feature (for those who loved to play in excel, etc, or who wanted to create a datawarehouse in sql, etc, all without us needing to write the exports individually) - first, a table defined what could be exported (table name, export file, export format, etc), then it identified all columns to be exported and if they were MV, which MV groups existed (by number). When a table was exported, it created both the parent and all child tables needed (the key to the child was the parent key and a line number). Worked perfectly and no doubt would in OI, if we didn't offer other solutions now. And all controlled by the end user, once a single window and a single export program was written.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=3EE1F0B5629769B88525749600120D0B|View this thread on the Works forum...]]