uhhh, sorry to bother you all. I've figured it out, or at least the nuts and
bolts of it. ...guess I was tired last night.
By the way, in case anyone else is trying to fiddle with Foxpro files, you
have to load the Foxpro driver via ODBC data sources.
Hi Ang,
As you've discovered, FoxPro and Visual FoxPro files come in 3 parts. The
DBF is the table itself, The CDX (if present) is the index file, and the FPT
is the contents of memo fields in the main table, if there are any. You
would not access the CDX and FTP files directly; the FoxPro data engine
reads them if it needs to.
You may also see a DBC which is a Database Container that holds metadata
about Visual FoxPro tables. (It's index and memo files are DBX and DCT.) If
the DBC file is present then you would want to set up the ODBC data source
to access a database rather than a free table directory.
There is also an OLE DB data provider for FoxPro and Visual FoxPro.

Signature
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com www.cindywinegarden.com
> uhhh, sorry to bother you all. I've figured it out, or at least the nuts
> and
> bolts of it. ...guess I was tired last night.
>
> By the way, in case anyone else is trying to fiddle with Foxpro files, you
> have to load the Foxpro driver via ODBC data sources.
>> How do I access (no pun intended) data in files with an extension of
> either
>> ".fpt" or ".cdx" ?
Ang - 17 Nov 2004 06:36 GMT
hmmm......
Thanks, Cindy... I understand the first paragraph.
But you're starting to lose me on your second paragraph. I understand the
concept of a table (dbf), an index (cdx), and a memo field (ftp). Can you
please explain a little further about database containers? {And of course,
like all curious people I sure would like to know why the "table - index -
memo" business was not good enough and had to be augmented with dbc's,
dbx's, and dct's??}
Thank you.
Ang
> Hi Ang,
>
[quoted text clipped - 10 lines]
>
> There is also an OLE DB data provider for FoxPro and Visual FoxPro.
Cindy Winegarden - 17 Nov 2004 23:24 GMT
Hi Ang,
The DBC allows for meta data (data about data) such as:
Field comments and captions
Persistent relationships
Field and record-level validation without writing code
Rules for referential integrity with cascading updates and deletes
Stored procedures
Views based on local and/or remote tables
Connections to remote data sources
Primary and Candidate keys
Long table and field names
Default values
Input masks
Triggers
You will find many of these same features in other databases such as
Microsoft SQL Server.

Signature
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com www.cindywinegarden.com
> hmmm......
> Thanks, Cindy... I understand the first paragraph.
[quoted text clipped - 5 lines]
> memo" business was not good enough and had to be augmented with dbc's,
> dbx's, and dct's??}