Create/convert a valid database .DBC file (VisualFoxPro) from Excel?

I have data in Excel that I need placed inside a VisualFoxPro table file (.DBC). (Long story)

I don't even know that much about .DBC files except that they are database like in structure and that I can read the table contents inside Excel by using Get External Data -> From Other Sources.

So is it possible to either:

1. Use VBA to convert the said Excel file into a DBC file? OR
2. Use VBA to extract data from Excel file into a new Access file which is programmatically set up to mimic a DBC internals and then rename the file extension of said Access file?

If you know of a solution, please supply code or a hyperlink to a webpage covering this topic. Thank you.

Hi,

It would seem to me that you would be better off trying to convert MS Access data to .dbc as they are both databases. I don't see any built-in Access conversion to Fox Pro but here is a site that might help.

http://www.sobolsoft.com/accessfoxpro/

Using Access you can either import or link to an Excel sheet and use the data just like it was in the Access database.

Originally Posted by MarvinP

you would be better off trying to convert MS Access data to .dbc as they are both databases.

Good point.

Originally Posted by MarvinP

I don't see any built-in Access conversion to Fox Pro but here is a site that might help. http://www.sobolsoft.com/accessfoxpro/

My fault. I forgot to specify in my opening post that I don't want to rely on any external software.

Taking a step back - how workable is it to create an Access database file by using Excel VBA? (The database would be populated from data within the Excel workbook)

Access can either link or import Excel data, easily.

Doing the whole thing from Excel VBA, you are on your own.

Originally Posted by MarvinP

Access can either link or import Excel data, easily.

I realise that and agree with what you say.

I am approaching this problem with the end users in mind. This create a valid database .DBC file is part of a bigger process. The end users already have to convert data between Excel and another program and then back again later on as part of the process required by this project ( yes, it would be better to have the entire process run in Excel but managerial decisions create the current situation). I wanted to avoid bringing Access into the picture as that would mean yet another program that the end uers would have to deal with (particularly as I know some of them have no idea on how to use Access).

So... if I can have a macro in Excel that will open Access as an external object and run it from Excels VBA then that is one less hurdle for the end users. (Similar to how it's possible to have Excel VBA open Word and create a new Word doc with data from Excel all from the Excel side - the end user doesn't need to touch Word).

Originally Posted by MarvinP

Doing the whole thing from Excel VBA, you are on your own.

Then I'll have to blaze a new trail across uncharted territory! Yee ha!

UPDATE: A solution to this thread is now a low priority.

Recently management decision was made that the end users would manually re-key the data from Excel to the other program rather than using a DBC file to export/import the data.

Since the thread is not solved, I will leave it open.