do I need relationships?

[John T (WI)]

I've been using "The missing manual" book for FM Pro 8 as my guide. From what I've read, my application doesn't need relationships, but maybe I'm wrong.

Here's what I've got. I've got one database that contains my company name and address, etc. A 2nd database that contains a contractors info and their buyers info. What I'm trying to do is generate form letters from these databases, different kind os form letters.

So trying to make a report layout, I try to use info from the my company database, and the contractors info from the 2nd database.

I indicated that the report (actually a letter) would be using the 2nd database primarily, and I have no problem having those fields show up in the report. When I try to use my companys info in the report tho, I see "" in the preview of the report.

So, exactly what kind of relationship do I need here? Do I need to make another layoutor table? with relationships of the fields in the other tables as its fields for making the report?

I could experiment, but I'd rather not futz around wasting time. I thought my requirements were relatively simple, so I didn't read the chapter on relationships in the "missing manual", just skimmed.

Thanks,

John

Can anyone set me straight?

[aldipalo]

In order to view data from 2 tables on the same layout the tables need to be related.

The question you need to answer, in order to relate the tables, is are company and contractor related? If so how? One to many? Many to many?

Then set up a unique key field that relates the two. Usually, an auto enter->serial number field in the primary table (The Parent) and a related key in the secondary table (The Child).

I would also suggest you go back and read the chapter on relationships. After all, the beauty and power of FM is it's a relational database.

If you post a blank copy of your database we might be able to help you more.

HTH

Al

[John T (WI)]

I read the chapter in the missing manual on relationships. I believe I know what I need to do now. Really opened my eyes to other things I can do with this database in the future!

John