foxbase
SigmaJT
maybe some of you have experience with it.
I am trying to get foxbase data into an excel spreadsheet and for whatever
reason it isn't able to be opened/converted by excel xp. So I want to use
the foxbase language to output the foxdata in a comma separated value format
that excel should be able to read easily
I guess I'd like it like this
record1,data,data,data,data,data,data
record2,data,data,data,data,data,data
.
.
.
I have tried typing help in foxbase and it hasn't been all that helpful, I
have searched for foxbase tutorials on yahoo which returns many hits but the
ones that seem like they'd be useful are down and the other ones don't
actually give tutorials
I've tried various tools to convert foxbase databases ?.dbf? to csv format
but they have all either crashed on the file or just not worked.
Any ideas?
-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----
Linc
>maybe some of you have experience with it.
>I am trying to get foxbase data into an excel spreadsheet and for whatever
>reason it isn't able to be opened/converted by excel xp. So I want to use
>the foxbase language to output the foxdata in a comma separated value format
>that excel should be able to read easily
>
>I guess I'd like it like this
>
>record1,data,data,data,data,data,data
>record2,data,data,data,data,data,data
>.
>.
>.
>
>I have tried typing help in foxbase and it hasn't been all that helpful, I
>have searched for foxbase tutorials on yahoo which returns many hits but the
>ones that seem like they'd be useful are down and the other ones don't
>actually give tutorials
>
>I've tried various tools to convert foxbase databases ?.dbf? to csv format
>but they have all either crashed on the file or just not worked.
>
>Any ideas?
Not real sure about foxbase, but I use foxpro all the time and in foxpro you
can do a:
copy to file.sdf type sdf
which would copy your data to a text file. As far as excel sheets go, usually
you can just rename the file extension from dbf to xls and open it up.
Fabio Giannotti
> Sent: Friday, January 04, 2002 11:50 AM
> To: distri...@xenitec.on.ca
> Subject: foxbase
>
>
> This is probably off topic, but Foxbase came with our SCO
> Unix 5.0.5 so
> maybe some of you have experience with it.
> I am trying to get foxbase data into an excel spreadsheet and
I regularly bring foxbase databases into excel with no problem. Just get
the .dbf on your windows box, and open it in excel. If this isn't working
there is either a problem with the file or excel. Did you load all of the
conversion options with excel? How are you getting the file from unix to
windows? If you are using ftp, did you turn binary on?
Good luck,
Fabio
SigmaJT
"Fabio Giannotti" <fab...@venmar.com> wrote in message
news:001701c19552$97061660$6700...@venmar.com...
There are programs written in foxbase by someone else that regularly access
and modify the .dbf file so I assume the file is good. I transfer the file
using ftp with binary on and excel pops up with a message saying the
database isn't in a recognizable format. It then attempts to import as a
text file but the job it does is nowhere near close to what it should be.
We have about 5000 records with about 30 fields each and excel ends up doing
something simalar to taking all the fields for about 50 records and placing
them in cell A1. Then next 50 to cell A2 and so on
Ben Rosenthal
> >This is probably off topic, but Foxbase came with our SCO Unix 5.0.5 so
> >maybe some of you have experience with it.
> >I am trying to get foxbase data into an excel spreadsheet and for whatever
> >reason it isn't able to be opened/converted by excel xp. So I want to use
> >the foxbase language to output the foxdata in a comma separated value format
> >that excel should be able to read easily
> >
> >I guess I'd like it like this
> >
> >record1,data,data,data,data,data,data
> >record2,data,data,data,data,data,data
> >.
> >.
> >.
> >
> >I have tried typing help in foxbase and it hasn't been all that helpful, I
> >have searched for foxbase tutorials on yahoo which returns many hits but the
> >ones that seem like they'd be useful are down and the other ones don't
> >actually give tutorials
> >
> >I've tried various tools to convert foxbase databases ?.dbf? to csv format
> >but they have all either crashed on the file or just not worked.
> >
> >Any ideas?
>
> Not real sure about foxbase, but I use foxpro all the time and in foxpro you
> can do a:
> copy to file.sdf type sdf
The SDF option gives you fixed length records. He asked for delimited with , to
try
copy to <file> delimited
This will give you comma delimited records.
>
> which would copy your data to a text file. As far as excel sheets go, usually
> you can just rename the file extension from dbf to xls and open it up.
Ben Rosenthal
Ben Rosenthal
As suggested earlier, try exporting to a text file.
COPY TO <file> TYPE SDF
Will result in a text file with fixed length records.
COPY TO <file> DELIMITED
Will result in a text file with comma delimited records.
Then import into excel.
Ben Rosenthal
Jeff Liebermann
>This is probably off topic, but Foxbase came with our SCO Unix 5.0.5 so
>maybe some of you have experience with it.
>I am trying to get foxbase data into an excel spreadsheet and for whatever
>reason it isn't able to be opened/converted by excel xp.
Foxbase is the dBase II clone.
Foxplus is the dBase III clone.
FoxPro is the yucky dBase IV clone.
Which FoxXXXX thing are you using?
I don't have Excel XP handy, but I just ran a quick check of a
database created with Foxplus 2.1.2 on SCO Unix 3.2v5.0.5. It opens
in Excel 97 SR-2, and Excel 2000 SR-1 directly.
I can't tell what's gone wrong on your end, but the suggestion of
exporting to SDF (system delimited format) is a good one.
--
Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
(831)421-6491 pgr (831)426-1240 fax (831)336-2558 home
http://www.LearnByDestroying.com WB6SSY
je...@comix.santa-cruz.ca.us je...@cruzio.com
Robert Carnegie
Our Excel 97 SR-2 _is_ perfectly happy to open Foxbase+ 2.1.1 files
renamed from *.dbf to *.xls . In case a DBF file has an obscure
defect in its header (our Recital DBMS does _not_ like these Foxbase+
files - "errno -220"), besides the techniques above you could consider
building a "clean" file by
. copy structure extended to mystructure
. create newfile from mystructure
. append from oldfile
"copy to newfile" might do equally well; I'm not sure.
It is sometimes possible to create a file with really silly faults,
such as multiple fields with the same name.
We seem to have a lingering Y2K thing in our Foxbase+ (perhaps
specifically 29.02.2000, existence or non-existence of); I think
my boss refused to apply the latest patch. Thus date() does not
work and lupdate() on new files is tomorrow and not today.
For that matter, in a newly created file, I see -
159$ hd rjac020114.dbf
0000 03 02 01 0f 01 00 00 00 a1 00 35 00 00 00 00 00 ..........5.....
0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020 46 4f 52 45 4e 41 4d 45 00 00 00 43 01 00 00 00 FORENAME...C....
0030 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040 53 55 52 4e 41 4d 45 00 00 00 00 43 15 00 00 00 SURNAME....C....
0050 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060 44 41 54 45 00 00 00 00 00 00 00 44 29 00 00 00 DATE.......D)...
0070 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080 4e 00 00 00 00 00 00 00 00 00 00 4e 31 00 00 00 N..........N1...
0090 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0 0d 20 52 6f 62 65 72 74 20 20 20 20 20 20 20 20 . Robert
00b0 20 20 20 20 20 20 43 61 72 6e 65 67 69 65 20 20 Carnegie
00c0 20 20 20 20 20 20 20 20 20 20 32 30 30 32 30 31 200201
00d0 31 34 31 32 2e 33 1a 1412.3.
00d7
- that a date field is held as characters 2002 01 14 (without the
spaces). Hmm - was this true in the old days, or wasn't it just
two bytes, counting days since 01-01-1900 or something like that?
Perhaps another reason to rebuild the file.
Tom Parsons
|
| We seem to have a lingering Y2K thing in our Foxbase+ (perhaps
| specifically 29.02.2000, existence or non-existence of); I think
| my boss refused to apply the latest patch. Thus date() does not
| work and lupdate() on new files is tomorrow and not today.
<snip>
This indicates you are using a version complied with the "old" libraries
that contained this error. The fix2000 binary repaired this issue
BUT that fix was rolled into the Y2K supplemnent for FoxBase.
| - that a date field is held as characters 2002 01 14 (without the
| spaces). Hmm - was this true in the old days, or wasn't it just
| two bytes, counting days since 01-01-1900 or something like that?
| Perhaps another reason to rebuild the file.
No. FoxBase always stored years as YYYY. Years were calculated by
adding 1 to 100 with 100 being 1900. This was fixed in the Y2K
supplement.
The most obvious Y2K problem was 2 digit entry fields would not
prepend the proper 2 digits to create the YYYY entry.
Upgrade.
--
==========================================================================
Tom Parsons t...@tegan.com
==========================================================================
Ben Rosenthal
Or sometimes unprintable control characters in the data areas of the file caused problems.
<cut>
Ben