Foxpro?

S

Stranger

I have a FoxPro application that I am trying to convert the database to access. I am able to import them but how do I relate the tables back together. I don't see anything that is unique.
 
C

Cindy Winegarden

In [email protected],
Stranger said:
I have a FoxPro application that I am trying to convert the database
to access. I am able to import them but how do I relate the tables
back together. I don't see anything that is unique.

Hi Stranger,

Sometimes FoxPro tables have a compound primary key - that is to say that
two fields together may make up the unique value that identifies the record.
Perhaps something like OrderNumber and OrderItemNumber.
 
S

Stranger

Any idea how to easily do this? I can see where one table has the same
number that match another table, for example: cont1 has a field called fidno
that matches the fidno in cont2 and cont1 has a field that matches fidno in
hist. there may be multiple numbers that are the same in each table. I am
very confused. :)

What I want to end up with is the tables related so I can easily pull the
data back together.
 
A

Albert D. Kallal

Any idea how to easily do this? I can see where one table has the same
number that match another table, for example: cont1 has a field called fidno
that matches the fidno in cont2

Likely, the above is the other way around.....cont2 has a field that relates
it BACK to the parent table called count1. (you will have to check the
original FoxPro design to really figure out which way you need to go!).

So, go to the relationships window, and start setting up your relations.
Drop in the parent table count1, and also the child table to count2. You can
then draw lines for the relationships between the tables.

You can also then drop in the additional table, and again, drop a line from
count1 to this table to the correct field (which way you draw the line is
important).

So, "child" tables are related back to the parent table with a field. So, if
a customer 123 purchased 10 items, then EACH record in the items purchased
table will have a field called cust_id with a value of 123 (so, many records
can be related back to the one customer..and thus the field will repeat the
customer number over and over).

To effect migrate relational data between systems, you need a good
understanding of the data structures to be able to glue them back together
after you transfer them. If you don't have a good diagram, or documentation
on how the tables are related..you certainly have a tough job ahead of you.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top