Sesame 1.1.4

I've finally taken time to get back to making some design changes...I'm doing something not quite right is my theory.  I wanted to redesign my subform so that the linking is natural rather than relational in hopes it would be more efficient.  There are 6000 + records in the subform and it increases daily. I exported my records, changed the subform properties, imported the data back in to Sesame and find I'm missing 2000 or so subform records...and my programming is running wierd...I have programmed a running total for subform records and it calculates, but the total stays in the element for only a fraction of a second...then it's blank.
My main concern (first things first) is to find out why I have records missing after importing back in to Sesame.  I was VERY careful to check for blank records prior to export...also careful about the order in which I exported and imported.

I'm wondering if I should export each database seperately rather than together as parent and child records?  I think Ray and I discussed this awhile back and I've just gotten time to work on it again.

BTW, as is stands linked relationally, everything runs fine though searches are very slow when Sesame has to search through thousands of records, etc.  

I'm thinking of a few different ways I might be able to acomplish what I want which involve importing into Q&A, re-translating, etc...which I can do if need be.

Any ideas appreciated.

Quote:


Hello again Ben,

Yes they were parented to my main form.  I made a note of the number of records I have in each dadabase prior to exporting.  The parent records came back perfectly.  I think it's something I'm doing/not doing with my subform records.  I haven' yet tried to export form each database in stand - alone mode.  Is that recommended when I would be importing back into the same application?  I know there are probably severa different ways to accomplish this.  I'm looking for the most correct one

Quote:


Ray,

Programming runs on Form Exit: 

Code:
CalculateParts()

Here's the Global Code:

SubRoutine CalculateParts()   
 
Var vCount as Int   
Var vTotal as Double   
Var vRecord as Int   
 
 
vRecord = 1 //Record variable   
 
vCount = @FormResultSetTotal("Repair1")   


If vCount > 0 Then   
{   
While vRecord <= vCount   
{   
//Loop through subrecords adding up totals.   
vTotal = vTotal + @TM(@FormFieldValue("Repair1", "Parts", vRecord))   

vRecord = vRecord + 1   
}   
 
//Place values in elements on form   
RepairTotal = vTotal   
}   

End SubRoutine

Quote:


I'll do that Ray...the code is working perfectly on my original application.  When I exported, redesigned with natural linking and imported my records back into the application is when this little problem appeared.  I'll get those files together asap.  Thank you.

Quote:


Charlie,

The element used to display the total was not bound to a field. So in essence, your programming was filling in the element and then throwing that value away because it had nowhere to store it.

Quote:


Ben,
A light bulb lit above my head a few minutes ago (dim as it may be).

I re-read what you and Ray were saying about those "missing" records...jogging my memory back about 7 years or so I realized that we have been repairing and keeping repair records on equipment from other departments that we do NOT have on our inventory.  There is no inventory record (parent) for some of our repair records; how many? maybe 2,000?  

I'll do some reading and see if there is a way (using our original application-or even our old Q&A database) to find these records.  I'm certain you've hit the nail on the head Ben...  I'll make a list of those departments and see if I can get a total on the nember of those records by a simple search through our database prior to exporting.  Thank you Ben...and, of course, "the one and the only"