You don't have to Trim at all.
Open Designer
Open your Merged DB
Save it as a DSR
Expand Forms
Expand Redesign Customize a form
Exapnd the folder underneath that(Your Parent Folder)
You will then see a folder named the same as your child.
Expand that folder
You will see a green dot under it. That is the subform.
Click the green dot the form that is the subform will open and you can make the changes you want.

-Ray

Just was at the home page.
I'm a little concerned.
If I order another licence, given that I already have the two, will it add one more user? Or will the disk I get be the same as the floppy I have now?

Quote:


It depends on the nature of the application. But, in general, Sesame will respond better to memory upgrades.

Quote:


You're welcome.

Quote:


Yes. Natural links will always be much faster than relational.

John,

You DEFINATELY want natural links if the speed of searches is a concern. (Not to mention that you will save yourself the overhead of maintaining the links between the two databases via programming.)

I started out with relational linking before I figured out how to generate natural linking for my imported Q&A data, and I found the same thing you did -- relational subforms are torture to search in.

I could not believe the difference in speed between the two methods. If you don't have to use relational linking, natural linking is the way to go!

Thanks, I've got some more reading to do.
The actual search time was not half an hour either, it has actually over an hour, I was out of the office, my Office Manager tells me it just finished as I came in the door.
I have to finish this up in the next few months, as I'm switching jobs. I'm leaving the corporation for other interests. I don't want to leave a mess behind. Besides, he/she would have to come back here, and ask you all these newbie questions over again.

There is almost certainly something else going on. I just built an application with 100,000 records on the main form, and the same number of records on the relational child form. The key field between them is numeric. The main form has 21 fields of average length, the child form only has two fields, one numeric, and the other a long string. On my computer (an older 800 Mhz intel with 128 Meg of RAM), the main form can do a single field string or numeric search between 5 and 7 seconds, returning all appropriate children. The .db file is 10,313,984 bytes and the .dat file is 31,223,932 bytes (well below swapping range). So while this isn't the largest application, it is a very large relation-set (any one parent may have any one (or more) of 100,000 children).

If you are seeing times much worse than this on a larger or faster machine, the problem is probably not merely the relational linking slowdown. It is probably some other bottleneck being multiplied by relational linking.