If you're looking for a one-time or infrequent solution, I think that
probably the easiest way to export the data is to use 4D's language
to export all the tables in ascii files with seperators. From there,
you can import into basically anything.
If you're looking to do this frequently and/or on live data, you
should
probably do like Scott Vanderbilt says and use ODBC on 4D Server.
You can also go the reverse route and use a plugin to, say, write the
4D data to MySQL or another SQL database like Oracle.
I second Scott's opinion that you shouldn't access 4D's datafile
without going through 4D.
Paul
On Mar 25, 9:09 am, "Scott Vanderbilt" <datagenic.li...@gmail.com>
wrote:
> > saying... ?- Hide quoted text -
>
> - Show quoted text -
I suggest you clarify this before investing time. If the 4D
application
is an application (or .exe on Windows), you can't use it without
getting
a non-merged version from the developer. Ideally, you could get source
code, which would enable you to integrate a routine for exporting the
data, without the need for 4D Server or ODBC.
Paul
http://www.committedsoftware.com/datacheck.html
-- Brad Perkins