Hello,

A relational subform search is going to take longer than a search on a parent form or a search on a Natural subform. How long it takes is going to depend on the number of child records and the number of parent records.

Mark, I'm sure will correct me if I am wrong on this, but a simplified rundown of my understanding of what is happening is as follows.
Sesame finds all records in the subform that match the retrieval criteria
Sesame then has to find all the parents for each one of those child records. Since each child record can have more than one parent Sesame must loop through all the parent records for each child record that matches the criteria, adding parent records to the result set that have not already been added.
Then for the First record Sesame must Search through all the records in the child database to find all the sub-records that are linked to that parent record.

If you have a large application, this can take some time and Sesame may appear as if it has frozen, when it is actually just running a search. The Mode box in the upper right should say Working and you should see Sesame using some CPU.

Is there any specific reason that you are using Relational linking and not natural linking?

-Ray

charliebrown wrote on Mar 23^rd, 2007 at 10:22pm:


Make a copy of your application files!
Export your records to ASCII
Redesign your application
Delete the data records
Redesign your form so it has a natural form where the relational form was
Save your design to a new application file (or reconcile to a copy of your app)
Import the ASCII file.

After all is done, if you choose, you can get rid of the key fields/elements, as they are no longer necessary. Some people choose to keep them just to make sure that everything matches up. But since it is no longer used to create the relation, it is no longer functionally necessary for Sesame.

Most importantly, WORK ON COPIES of your files.

Under 1.x naturally linked records have a great speed advantage. If your relation is one to many, the natural choice is natural linking.

Quote:


Oh yes!  Copy and backup everything FIRST...that I always do.  My coworker, wants to get into the designer and "make it look......" who knows what he's got cooking in his cranium?  In any6 event, I said, "Sure!  Here's the manual, and I'll put a copy of the db in your directory....LEAVE THE MASTER DATABASE ALONE UNTIL I TEST WHAT YOU HAVE DONE!!!!!!!!!!!!!!  understand? 

he doesn't understand why I'm so "protective" ...if he works in the master db, HE WILL     

You will want to export from the highest level form and include all the subforms and elements therein. It will take a while if there are a lot of forms / records / elements / fields. If you are experience field missmatch, make double-sure that you are importing in the same order as you exported.

Quote:


I had to put off some work on our database to do what these folks actually hired me to do (the nerve of some people
I've discovered a couple of things:  My database is corrupt to some extent...I've exported and imported our data numerous times and have, for lack of a better term, a mess...the number of records imported is way off-too many repair records and less inventory records.  I have "money" in my date fields; just a few examples.  I was reading through the text files of my exported data and there are some very strange fields there...it "appears" someone was trying to search in the add data mode using the .."search" spec and it has been stored as a record...little things like that...grrrrrrr...(I know, trash in, trash out)

I'm looking at a couple of alternatives...go through each of the 7000 or so records and clean this mess up or go back to the original Q&A database and clean it up there and translate again.  (I think some of this mess may have been there when I Translated to Sesame originally, though I followed the Translation guide to the letter and had no issues then).  I also wonder if any of our saved reports from Q&A are having an impact on the export/import problems I'm experiencing?  I was very careful in exporting/importing in the exact order, etc.

We've added somewhere around 100 new records since we started using Sesame, so it would be some work, though not a huge amount for me to fire up the espresso machine and re-enter the newest data.

Quote:


Looking back at my post, rather than my database being corrupt, I should have said that I think I may have imported some corrupt data from Q&A when I translated into Sesame.  I'm quite certain it has nothing to do with Sesame but rather some bad data I imported from Q&A.  The translation process went smoothly-no errors or glitches.  I noticed what appears to be "blank" records as well as the items I listed before when viewing the exported text file.

I did send my data files in to support for a different reason last Friday.  I can send again if need be.  Thanks for offering to look things over.  I'll be working on my end as well.  

I might add that our my Sesame program is running fine.  Searches are good, what elementary programming I have runs great.  I am curious as to how it will run when I change to natural linking:)  I have a very strong feeling it will speed things up considerably.  Thanks....*again*

The weather this year has been incredible...hope everyone is doing ok there...had high winds here, but nothing compared to the east.

I understand regarding the differences in the way Sesame and Q&A "see" data...one question that I popped into my mind was if it is necessary to have LE exported in the same order in both parent and subforms where they contain identical data-in my case I have Make, Model, Serial Number and several other LE that contain related data.
I just tried an expor/import again after cleaning out what questionable entries I could find...Inventory came back almost perfectly...subform records were almost double the number I had exported when the Import was complete.  Not sure if that is a "clue" as to what I may be doing wrong 

No rush on this Mark...we're operating and able to add and retrieve data here.  Just trying to make things as good as they can be in the long run.   Thanks for your help-take care of your priorities.  Power outages are no fun.
Charlie