|
| Re: Export data table to lower table level |
 |
Sun, 17 Feb 2008 20:58:58 -080 |
Pieter van Heeren wrote:
> I need to export the data table level 7 to a lower level for pickup by
other data management programs, spreadsheets or GIS. dBASE III format seems to
be the one with the widest range of compatibility and exporting throught the
COPY command (TYPE DBMEMO3) the way to go. However, the record size of 1423
bytes over 157 columns is more than dBASE 111 format accepts, so some columns
are lost.
>
> Exporting to a text file is awkward as the user has to write headings for
the columns, or does the Ken Mayer Exportdata.wfm in the DUFLP solve this
problem. (I know I should have tested this - sorry, I will straight after this
has been posted). With a file this size one wants the user to have the least
possible hassles.
>
> Please advise.
>
> Perhaps I have missed something. The Updateset class does not allow a dbf
table copied to another level than the origional level. Is this so and is it an
updateset limitation or a BDE limitation?
ExportData and UpdateSet do not do this. However, I recall that there's
a routine in the dUFLP to copy to a level 4 table ...
Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/
*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm
|
| Post Reply
|
| Export data table to lower table level |
 |
Sun, 17 Feb 2008 22:41:54 -050 |
I need to export the data table level 7 to a lower level for pickup by other
data management programs, spreadsheets or GIS. dBASE III format seems to be the
one with the widest range of compatibility and exporting throught the COPY
command (TYPE DBMEMO3) the way to go. However, the record size of 1423 bytes
over 157 columns is more than dBASE 111 format accepts, so some columns are
lost.
Exporting to a text file is awkward as the user has to write headings for the
columns, or does the Ken Mayer Exportdata.wfm in the DUFLP solve this problem.
(I know I should have tested this - sorry, I will straight after this has been
posted). With a file this size one wants the user to have the least possible
hassles.
Please advise.
Perhaps I have missed something. The Updateset class does not allow a dbf table
copied to another level than the origional level. Is this so and is it an
updateset limitation or a BDE limitation?
|
| Post Reply
|
| Re: Export data table to lower table level |
 |
Mon, 18 Feb 2008 01:10:16 -050 |
In article <QFrg0AecIHA.1880@news-server>, psvh@mweb.co.za says...
> I need to export the data table level 7 to a lower level for pickup by
other data management programs, spreadsheets or GIS. dBASE III format seems to
be the one with the widest range of compatibility and exporting throught the
COPY command (TYPE DBMEMO3) the way to go. However, the record size of 1423
bytes over 157 columns is more than dBASE 111 format accepts, so some columns
are lost.
>
> Exporting to a text file is awkward as the user has to write headings for
the columns, or does the Ken Mayer Exportdata.wfm in the DUFLP solve this
problem. (I know I should have tested this - sorry, I will straight after this
has been posted). With a file this size one wants the user to have the least
possible hassles.
>
> Please advise.
>
> Perhaps I have missed something. The Updateset class does not allow a dbf
table copied to another level than the origional level. Is this so and is it an
updateset limitation or a BDE limitation?
Pieter,
Perhaps .CSV files would be the answer. There is no limit to the number
of columns you can export to them and they are readable by all
spreadsheet programs and many other types of software, too.
--
Geoff Wass [dBVIPS]
Montréal, Québec, Canada
.|.|.| dBASE info at http://geocities.com/geoff_wass |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.
|
| Post Reply
|
| Re: Export data table to lower table level |
 |
Mon, 18 Feb 2008 12:04:07 -050 |
Ken Mayer [dBVIPS] Wrote:
> Pieter van Heeren wrote:
> > I need to export the data table level 7 to a lower level for pickup by
other data management programs, spreadsheets or GIS. dBASE III format seems to
be the one with the widest range of compatibility and exporting throught the
COPY command (TYPE DBMEMO3) the way to go. However, the record size of 1423
bytes over 157 columns is more than dBASE 111 format accepts, so some columns
are lost.
> >
> > Exporting to a text file is awkward as the user has to write headings
for the columns, or does the Ken Mayer Exportdata.wfm in the DUFLP solve this
problem. (I know I should have tested this - sorry, I will straight after this
has been posted). With a file this size one wants the user to have the least
possible hassles.
> >
> > Please advise.
> >
> > Perhaps I have missed something. The Updateset class does not allow a
dbf table copied to another level than the origional level. Is this so and is
it an updateset limitation or a BDE limitation?
>
> ExportData and UpdateSet do not do this. However, I recall that there's
> a routine in the dUFLP to copy to a level 4 table ...
>
> Ken
>
> --
> /(Opinions expressed are purely my own, not those of dataBased
> Intelligence, Inc.)/
>
> *Ken Mayer* [dBVIPS]
> /Golden Stag Productions/
> dBASE at goldenstag dot net
> http://www.goldenstag.net/GSP
> http://www.goldenstag.net/dbase/dBASEBooks.htm
> http://www.goldenstag.net/dbase
Thanks, the duflp copy4 module worked!
|
| Post Reply
|
|
|
|
|
|
|
|
|
|