Hi, I am the manager of a cemetery. We have four databases running in QA4, that I would like to import, and integrate into Sesame, so that I can pull records from each into one form.
I have no difficulty in converting the databases into sesame format, but I'm lost when it comes to linking them up, and the best way to go about it.
The basic way it's layed out now,
The Lot register contains the owners contact information, and notes on general lot info. This I would like to be the main area, from wich, I can call the others, is that the best way to do it, or should I design a new Database, and use all the former Q&A databases as sub databases?
The others, are the Burial register, with over 15000 entries each giving the genealogical information of a burial.
The Flower database, giving contact information for whoever is looking after the flowerbed, if any for the lot, and used for mail merge operations. (May or may not be the same as the lot owner info.
The Pre-need database, that gives information on services that have been prepaid for that lot.
The winter wreath database, much the same as the flower database, also used for mail merge 

What I'd like to be able to do, is search the main database by lot owners name, and pull up from that any information i need about the lot from the other databases.
For example, I'd like to be able to ask for, and get, a list of all the burials in the lot, and the grave numbers they are in.
When this was attempted in QA4, it would retrieve the first burial it came to, and stop. This was not acceptable, and we never did find a way around it. We ended up using each database separately, a major PIA.
I have been working with sesame off and on for some months now, but I can't figure out how to integrate these databases the best way.
In fact, I can't figure how to get an existing database to be a sub database.

John,

How about starting slow and simple to get some solid experience with Sesame and then figure out how to deal with your entire project.

Start by making a new application
Open Sdesigner
Click new application
In the filename box type CEM
Click on forms
Click design a form
Click add new database
Create new text element named LotOwnerName
Click save layout design
Click close design tab
Click add new database
Add new element LotNumber
Click save layout design
Click close design tab
Click redesign a form
Select form newdatabase
Click form named newform
In element adder click select element type subform
In the label box enter subformlot (or anything you like to call it)
Click add element to form
A new box will pop up step 1 will be select a form
click the down arrow and select NewForm0
leave step 2 and 3 alone
step 4 type a name
in step 5 change form to table using down arrow
click ok and place and size the new subform element on your form
Click save layout design

Click close design tab

Now you can open the application named CEM enter a lot owner name
And enter lot numbers relating to that owner.

When you later search by lot owner all the associated lot numbers will show.

You can add as many fields to the subform as you need and you can add additional subform elements to display whatever you need.

This example should give you an understanding of how to progress.

You can definitely make your form prettier and name things nicer and improve this but this should show you the basic principles involved.

Hope this helps.

If you are talking about adding elements to the subform just open the application in Sdesigner and click forms then redesign customize a form and choose the database form you want to add elements to. 


If you are talking about adding data to the subforms from the parent record just enter it in the field. Press f10 to enter another. Sesame handles the stuff that links the child data to the parent for you in the example I used.

John,

I have the example above application working on my machine.

If I add an owner name of smith to the main record
Then click in subform and enter lot 69
Press f10 and enter 70

Then go back to main enter another new owner jones
Then click in subform and enter lot 150
Press f10 and enter 160

Exit database

When I go to the main database and search for jones it brings up 150 and 160 in the database.

Am I not understanding what you are wanting to do?

Ok, I just went through and created the database exactly as you described, and it worked perfectly.
The trouble is, it looks exacltly like the one I made with the data already in the databases, except that mine does not work.
Is there a way I can compare the two side by side to see my mistakes?

Quote:


Yes, i'm afraid that's the way It has to be done, I have five fairly large databases that I have translated fron QA4, and I want to be able to get at the data from each from one form.

Quote:

Bob, I suspect that he should set the subform relational and specify the key fields - temporarily. Then once he has imported his data under the proper parent, he should set it back to natural linking. That way he avoids the ongoing "housekeeping".

This isn't something that happens automatically by changing the link type. It is a process you can do. Several Forum members have done it and say it works quite well. It works like this:
1. Create the relational link
2. Do a hierarchical export of the data.
3. Delete the relational link
4. Create a natural link
5. Do a hierarchical import of the data.