Hi all -

Is there a way to create dBASE files from OI?

TIA,

Mike O.

See this thread

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

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

Mike O.

You can read and write using ADODB. You can even create tables.

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

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

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.

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

Regards,

Mike O.

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

I didn't know that DBase was still around.

Ray Chan

And how about multivalue fields? dBASE does not support multivalue fields.

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.

View this thread on the Works forum...