Discussion:
FoxPro and DBaseIII
(too old to reply)
@HOME
2005-01-26 19:25:39 UTC
Permalink
Hi,

i'm at a new job where a ordering program is build in clipper with a
database in dbase III. Ofcourse ; ) i want to rebuild this in vfp. I am
using VFP 6.0. This is a rather huge application, and i don't want to
rebuild it at once. I figured i first build the gui just for lookup
functions. Add's and edit still remain in clipper / dbase III.

After finishing these screens, i can go on with the edit interfaces and add
/ edit functionality.

Now my problem: after opening the dbf files in FoxPro, i can not open them
anymore in dbase III.
I tried: set compatible db4 (there is no db3...) but that didn't work.

Is there a way to make this work?

Help will very much be appreciated!!!!

Rotsj
Rick Bean
2005-01-26 22:23:45 UTC
Permalink
Rotsj,
Just opening the tables shouldn't cause a problem. Although if you are using index files (e.g. .NTX, .MDX?), VFP won't work with them, it'll create it's own .CDX file. Clipper did have the ability to use an RDD (?) that allowed it to use FoxPro .CDX files - you may have to start there if you want to share these files.

Rick
Post by @HOME
Hi,
i'm at a new job where a ordering program is build in clipper with a
database in dbase III. Ofcourse ; ) i want to rebuild this in vfp. I am
using VFP 6.0. This is a rather huge application, and i don't want to
rebuild it at once. I figured i first build the gui just for lookup
functions. Add's and edit still remain in clipper / dbase III.
After finishing these screens, i can go on with the edit interfaces and add
/ edit functionality.
Now my problem: after opening the dbf files in FoxPro, i can not open them
anymore in dbase III.
I tried: set compatible db4 (there is no db3...) but that didn't work.
Is there a way to make this work?
Help will very much be appreciated!!!!
Rotsj
Dan Freeman
2005-01-27 00:57:23 UTC
Permalink
Actually, if you create standalone IDX indexes the apps can coexist but any
updates done from VFP will leave the clipper NTX indexes out of synch, and
vice-versa.
Post by Rick Bean
Rotsj,
Just opening the tables shouldn't cause a problem. Although if you
are using index files (e.g. .NTX, .MDX?), VFP won't work with them,
it'll create it's own .CDX file. Clipper did have the ability to use
an RDD (?) that allowed it to use FoxPro .CDX files - you may have to
start there if you want to share these files.
Rick
Post by @HOME
Hi,
i'm at a new job where a ordering program is build in clipper with a
database in dbase III. Ofcourse ; ) i want to rebuild this in vfp. I
am using VFP 6.0. This is a rather huge application, and i don't
want to rebuild it at once. I figured i first build the gui just for
lookup functions. Add's and edit still remain in clipper / dbase III.
After finishing these screens, i can go on with the edit interfaces
and add / edit functionality.
Now my problem: after opening the dbf files in FoxPro, i can not
open them anymore in dbase III.
I tried: set compatible db4 (there is no db3...) but that didn't work.
Is there a way to make this work?
Help will very much be appreciated!!!!
Rotsj
Mike Pratt
2005-01-27 16:26:41 UTC
Permalink
Hi Rotsj,

I am currently porting Clipper Summer 87 apps to xHarbour. Clipper and
VFP don't use the same indexing and don't respect each others record
locking. xHarbour is open source, for more info:
http://www.xHarbour.org

Regards,

Mike

P.S. As long as you don't make changes to the structure of your tables
or add them to a database container, you can access your data from
both Clipper and VFP.
Post by @HOME
Hi,
i'm at a new job where a ordering program is build in clipper with a
database in dbase III. Ofcourse ; ) i want to rebuild this in vfp. I am
using VFP 6.0. This is a rather huge application, and i don't want to
rebuild it at once. I figured i first build the gui just for lookup
functions. Add's and edit still remain in clipper / dbase III.
After finishing these screens, i can go on with the edit interfaces and add
/ edit functionality.
Now my problem: after opening the dbf files in FoxPro, i can not open them
anymore in dbase III.
I tried: set compatible db4 (there is no db3...) but that didn't work.
Is there a way to make this work?
Help will very much be appreciated!!!!
Rotsj
Loading...