Hi all,

I'm in my office this weekend, importing *everything* into Sesame, and I have a question.

I've switched my notes subtable to natural linking, and that has sped things up immeasurably.  However, the way I use my payment subtable, it has to be relational.  With it searching 110,000 payments (and growing at a rate of about 100 a day), it takes a few seconds between records -- not a huge problem, but it will cost me productivity.  However, only 1 in 10 accounts has payments.  I could flag my files as paid or not -- is there a way to turn off that subtable if there is no flag?

Thanks!


Is there a way to turn off

Hi!

Here's the reason my payment has to be relational (to my foggy thinking).

1) I have a payment admin screen that tracks about 60 fields of payment data (if we've released the payment to the client, what salesman gets credit, etc.).  Payment are entered on this form.

2) I have a second form in the payment database which is 5 fields (payment here, payment dir, payment date, paymentID, and payment ref). 

That is used in a subtable of my contact management field so staff can quickly see what they've paid, and for my contact management form to calculate the balance owing.

3) In my progress to turn a relational subtable into a natural subtable, I have to import Q&A to a relational Sesame database, and then export it, and then re-import it into a natural sesame database.  If I do this with my payments, I'll lose all my data, on the payment admin form, right?

Will do!

(You realize you're complaining about the cold to a Canadian, right?  )

Brrr!  That *is* cold!

You've got one of those grand old houses with a great porch, old world charm, and a huge heating bill, right?  I know the feeling ...

No luck, Mark.

Just reconciled with the following code on form entry:

// Experiment to hide Payment Subform if there are no payments -- BW 2005-11-20

if DBPd >0 then
{
	SubFormVisibility("Pmt Data",1)
}
Else SubformVisibility("Pmt Data",0)
 

It's not sorting the invisible data anymore, but there is still a noticeable lag as it searches the payment database for available payments. 

Maybe Erika will have a suggestion after the weekend?

I'll have to try that ...

I'm already duplicating my efforts by posting the payment information to my contact management screen when the payment happens, and the subrecord is just there to keep things accurate "on the fly". 

Thanks!