ms access table to "dBase IV" with index .cdx

[NuBie via AccessMonster.com]

i know this is weird but...we have existing foxpro application and some of
the data are from access 2000. ()

i need to export ms access table to "dBase IV" format inculding index. (.dbf
and .mdx) the code below exports the table to .dbf but how can i export the
index too (.mdx)

DoCmd.TransferDatabase acExport, "dBase IV", "c:\", acTable, "UserActivity",
"test.dbf", False, False

 

[NuBie via AccessMonster.com]

nobody knows?

i know this is weird but...we have existing foxpro application and some of
the data are from access 2000. ()

i need to export ms access table to "dBase IV" format inculding index. (.dbf
and .mdx) the code below exports the table to .dbf but how can i export the
index too (.mdx)

DoCmd.TransferDatabase acExport, "dBase IV", "c:\", acTable, "UserActivity",
"test.dbf", False, False

 

[Steve Sanford]

I searched for over an hour and all I found was:

http://msdn.microsoft.com/en-us/library/aa164086(office.10).aspx

There is a paragraph at the end that says:

"If you want to supply index information for a linked FoxPro or dBASE table,
first link the FoxPro or dBASE table by pointing to Get External Data on the
File menu and clicking Link Tables, then specify the indexes in the dialog
boxes for this command. Microsoft Access stores the index information in a
special information (.inf) file, located in the Office folder (the path is
C:\Program Files\Microsoft Office\Office). You can then delete the link to
the linked table. The next time you use the TransferDatabase action to link
this FoxPro or dBASE table, Microsoft Access uses the index information that
you've specified."

--------------------
BE SURE TO TRY THIS ON A *COPY* OF YOUR DBF FILE!
--------------------

You don't say if you are adding the data to a currently existing dbf file or
creating a new dbf file from the Access data. The index in the MDB doesn't
really matter when you export the data to the DBF file.

I used dBase III, III+ and IV back in the day. I never had a copy of Foxbase
so I am not sure if the following ideas will work....

- If you are creating a NEW DBF file:
Export the Access data to the new DBF file. Start Foxbase and
write a .PRG that will create the index(s) on the DBF.

- If you are appending to an existing DBF file:
The existing DBF should already have an index (.mdx) created.
Export the Access data to a new DBF file - zTemp.DBF or
somthing like that. Write a .PRG that will append the records
in the zTemp.DBF file to the actual data DBF, then reindex the
DBF.



HTH

 

[NuBie via AccessMonster.com]

Thank you Steve, i'll try this one.

I searched for over an hour and all I found was:

http://msdn.microsoft.com/en-us/library/aa164086(office.10).aspx

There is a paragraph at the end that says:

"If you want to supply index information for a linked FoxPro or dBASE table,
first link the FoxPro or dBASE table by pointing to Get External Data on the
File menu and clicking Link Tables, then specify the indexes in the dialog
boxes for this command. Microsoft Access stores the index information in a
special information (.inf) file, located in the Office folder (the path is
C:\Program Files\Microsoft Office\Office). You can then delete the link to
the linked table. The next time you use the TransferDatabase action to link
this FoxPro or dBASE table, Microsoft Access uses the index information that
you've specified."

--------------------
BE SURE TO TRY THIS ON A *COPY* OF YOUR DBF FILE!
--------------------

You don't say if you are adding the data to a currently existing dbf file or
creating a new dbf file from the Access data. The index in the MDB doesn't
really matter when you export the data to the DBF file.

I used dBase III, III+ and IV back in the day. I never had a copy of Foxbase
so I am not sure if the following ideas will work....

- If you are creating a NEW DBF file:
Export the Access data to the new DBF file. Start Foxbase and
write a .PRG that will create the index(s) on the DBF.

- If you are appending to an existing DBF file:
The existing DBF should already have an index (.mdx) created.
Export the Access data to a new DBF file - zTemp.DBF or
somthing like that. Write a .PRG that will append the records
in the zTemp.DBF file to the actual data DBF, then reindex the
DBF.

HTH

nobody knows?

[quoted text clipped - 7 lines]