Using Clipper Files in Access
H. Dederichs
Is there anyone who knows how to link or import Clipper-dbf databases into
Access95 or Access97,
where there index files are in ntx format?
J. Mario Pires
In article <64f00g$9...@tim.xenologics.com>, "H. Dederichs"
I am also interested.
Thank you.
Best Regards
J. Mario Pires
---
Please answer me by email also
Maksimovic Petar
J. Mario Pires wrote:
I am working on a database for one company, and I got in legacy of
previous programmer a bunch of *.dat and *.idx files. And a little
utility called DBU. I've been told that main exe application for that
files was written in Clipper 5.0, and I renamed *.dat files into *.dbf
(and it was just dbf's) and *.idx into *.ntx (and it was just idx's) and
linked them into Access 97 database as Dbase III or Dbase IV files
without any kind of problems. I also tried to import that DBF's so I
can change their design, and it worked just fine...
Greetings from Belgrade...
Petar
keon
There is a clipper ODBC driver that works for Access in this evaluation
download. If it is stiill
there.
http://www.intersolv.com/PRODUCTS/data-odbc.htm
J. Mario Pires <st...@cfn.ist.utl.pt> wrote in article
<64svbu$k04e...@cfn.ist.utl.pt>...
J. Mario Pires
In article <34722604...@eunet.yu>, Maksimovic Petar <cik...@eunet.yu> wrote:
>...
>I am working on a database for one company, and I got in legacy of
>previous programmer a bunch of *.dat and *.idx files. And a little
>utility called DBU. I've been told that main exe application for that
>files was written in Clipper 5.0, and I renamed *.dat files into *.dbf
>(and it was just dbf's) and *.idx into *.ntx (and it was just idx's) and
>linked them into Access 97 database as Dbase III or Dbase IV files
>without any kind of problems. I also tried to import that DBF's so I
>can change their design, and it worked just fine...
Thank you.
There is something that isn't clear to me: you say that the IDX files were
simply NTX's and Access reconigsed those Clipper Index files without
problems?
We all know that Clipper uses the same data format as Dbase, the problem are
(could be?) the index files.
Thank you again.
itrc
J. Mario Pires wrote:
>
> In article <34722604...@eunet.yu>, Maksimovic Petar <cik...@eunet.yu> wrote:
> >...
> >I am working on a database for one company, and I got in legacy of
> >previous programmer a bunch of *.dat and *.idx files. And a little
> >utility called DBU. I've been told that main exe application for that
> >files was written in Clipper 5.0, and I renamed *.dat files into *.dbf
> >(and it was just dbf's) and *.idx into *.ntx (and it was just idx's) and
> >linked them into Access 97 database as Dbase III or Dbase IV files
> >without any kind of problems. I also tried to import that DBF's so I
> >can change their design, and it worked just fine...
> There is something that isn't clear to me: you say that the IDX files were
> simply NTX's and Access reconigsed those Clipper Index files without
> problems?
>
> We all know that Clipper uses the same data format as Dbase, the problem are
Yes, the indexes are a problem. Access does not recognize the Clipper index
format. Clipper can use the dBase indexes, but it the existing app doesn't,
you're in trouble. Importing is not problem, Access ignore the index pretty
much. In linking use the dBase IV file format and skip the indexes. Don't do
anything to the source data that could screw up the native indexes.
I've been developing an Access app that is attached to an existing Clipper
program. We've had to be very careful to do client entry and updating through
Clipper, then do our extra stuff with Access.
I would rewrite the Clipper app into Access if there were time.
best,
tim
--
Tim Mills-Groninger
Chair, Technology Resource Consortium (TRC) http://www.igc.apc.org/trc/
Associate Executive Director
Information Technology Resource Center (ITRC) http://www.npo.net
6 N. Michigan Ave, Suite 1405
Chicago, IL 60602
voice: 312/372-4872
fax: 312/372-7962
email: it...@igc.apc.org
Nexa
J. Mario Pires wrote:
> There is something that isn't clear to me: you say that the IDX files were
> simply NTX's and Access reconigsed those Clipper Index files without
> problems?
>
> We all know that Clipper uses the same data format as Dbase, the problem are
> (could be?) the index files.
>
> Thank you again.
>
> Best Regards
>
> J. Mario Pires
> ---
> Please answer me by email also
Andas um pouco longe de casa, nao? :)))
E' bom encontrar gente do "fim do mundo" por estes lados... :) Estou em
Entrecampos. O IST esta' porreiro?
Irei dar a resposta em Ingles...
Firstly I don't know if you're doing it using menus or programming
modules.
As far as I know, .DBF's are equal in Clipper or DBase, so, if you're
importing/linking by menus, it's just easy.
By other hand, in code you can see some example how doing it on:
help -> search => TransferDatabase action
Still, in case you fell better using macros, there's the action =>
TransferDatabase, the rest is very intuitive.
Anyway, don’t forget that the Clipper .DBF are the same than the DBase
files.
About the index files, I think it's better to import the .DBF and the
create in Access the indexes inside the Table after import.
It's better and cleaner, for me! :)
--
Um abraco or greetings,
Nexa ** Remove - nospam - from my e-mail address **