ExplodedKeys for filtering

[LaRetta]

Hi Ugo,

My mind is in a swirl. It works (LineItems to LineItems2) using a global in the middle!! Well there goes everything I THOUGHT I was learning about 7. My understanding was that if the line ended in | then data (thus the relationship) would not flow back that direction. Every line end - backwards towards Pickup on my graph - displays a | but yet the portal displays (sort of).

Thanks for teaching me this! It won't refresh properly (I'm using 7.02 still). Entering Preview or Find won't even fix it (and that usually fixes all my portal refresh issues). It's only when I change data in a record that it changes the portal display. Even changing to the next Pickup record (different Contact) won't change it - it stays on the original gProductName. A very stubborn relationship it is!

I also plan to take full advantage of Mike's Exploded Keys. After I added that CF calculation to LineItems, my file size jumped from 400 to 852 so I was concerned. However after it refreshed for display in the Pickup portal (indexed it?), it dropped to 638 (but still too much).

I had used: ExplodedKey(ProductDescription) &

[Ugo DI LUCA]

It won't refresh properly (I'm using 7.02 still). Entering Preview or Find won't even fix it (and that usually fixes all my portal refresh issues). It's only when I change data in a record that it changes the portal display.

That's why the flush cached join results was such an important step with 7.03 actually.

The Exit Record/Request in FM6 was sufficient as a relationship was based on a max of 2 files. With 7, Commit Record/Request only refreshes the first join, but when more than one relation, and specially when a "deviation" is introduced as in this case, all "Left" keys are updated with the flush.

[Ugo DI LUCA]

It won't refresh properly (I'm using 7.02 still). Entering Preview or Find won't even fix it (and that usually fixes all my portal refresh issues). It's only when I change data in a record that it changes the portal display.

That's why the flush cached join results was such an important step with 7.03 actually.

The Exit Record/Request in FM6 was sufficient as a relationship was based on a max of 2 files. With 7, Commit Record/Request only refreshes the first join, but when more than one relation, and specially when a "deviation" is introduced as in this case, all "Left" keys are updated with the flush.

[Ugo DI LUCA]

It won't refresh properly (I'm using 7.02 still). Entering Preview or Find won't even fix it (and that usually fixes all my portal refresh issues). It's only when I change data in a record that it changes the portal display.

That's why the flush cached join results was such an important step with 7.03 actually.

The Exit Record/Request in FM6 was sufficient as a relationship was based on a max of 2 files. With 7, Commit Record/Request only refreshes the first join, but when more than one relation, and specially when a "deviation" is introduced as in this case, all "Left" keys are updated with the flush.

[LaRetta]

My hesitation in upgrading is this ...

The current solution is running nicely; no problems whatsoever. I figure I will need a block of time to upgrade my home system and test it thoroughly. Why? Because I'm unsure if FM's fixes will interfer with my work-arounds. I feel I should test it first. Then, I'll need to upgrade each station. And I simply haven't had a block of time to do it.

And much of my solution is handled by SecureFM (particularly windowing, menu control and layouts) and I'm unsure if their version will match perfectly as well. Maybe a bit paranoid but I just want to be sure. I simply refuse to upgrade and have it immediately hosted only to find out something is misbehaving. I can't fix it while it's being hosted and I can't kick everyone off while I attempt to resolve issues (business can't afford downtime).

Yep, I had an 'Ah Hah' moment the first time I read about 7.03's fix of adding the flush cache. And I was incorrect ... we're still using vs. 7.01.

LaRetta

[LaRetta]

My hesitation in upgrading is this ...

The current solution is running nicely; no problems whatsoever. I figure I will need a block of time to upgrade my home system and test it thoroughly. Why? Because I'm unsure if FM's fixes will interfer with my work-arounds. I feel I should test it first. Then, I'll need to upgrade each station. And I simply haven't had a block of time to do it.

And much of my solution is handled by SecureFM (particularly windowing, menu control and layouts) and I'm unsure if their version will match perfectly as well. Maybe a bit paranoid but I just want to be sure. I simply refuse to upgrade and have it immediately hosted only to find out something is misbehaving. I can't fix it while it's being hosted and I can't kick everyone off while I attempt to resolve issues (business can't afford downtime).

Yep, I had an 'Ah Hah' moment the first time I read about 7.03's fix of adding the flush cache. And I was incorrect ... we're still using vs. 7.01.

LaRetta

[LaRetta]

My hesitation in upgrading is this ...

The current solution is running nicely; no problems whatsoever. I figure I will need a block of time to upgrade my home system and test it thoroughly. Why? Because I'm unsure if FM's fixes will interfer with my work-arounds. I feel I should test it first. Then, I'll need to upgrade each station. And I simply haven't had a block of time to do it.

And much of my solution is handled by SecureFM (particularly windowing, menu control and layouts) and I'm unsure if their version will match perfectly as well. Maybe a bit paranoid but I just want to be sure. I simply refuse to upgrade and have it immediately hosted only to find out something is misbehaving. I can't fix it while it's being hosted and I can't kick everyone off while I attempt to resolve issues (business can't afford downtime).

Yep, I had an 'Ah Hah' moment the first time I read about 7.03's fix of adding the flush cache. And I was incorrect ... we're still using vs. 7.01.

LaRetta

[LaRetta]

Okay folks, I need to set something straight. I've been up since Saturday morning. And I may have read that file size wrong after adding Ender's Custom Function.

Because I compacted and optimized it just now before uploading for them to use at the office and the file size is now 411! Did I hallucinate, dream and work simultaneously, see it wrong (my eyes are bad) ... or did compact/optimize cut the size in half? I doubt it.

I changed ExplodedPermutation to > 4 (I hope that was the right change, Mike). But my portal in Pickup works perfectly and instantly!

In fact, I'm going to add this same feature so staff can type part (interior) of product word and display all Contacts that have ordered it! If I wasn't so darned tired, I'm be on-the-ceiling excited!!

They are going to be tickled at work when they see this!! God, I love this business!!

LaRetta

[LaRetta]

Okay folks, I need to set something straight. I've been up since Saturday morning. And I may have read that file size wrong after adding Ender's Custom Function.

Because I compacted and optimized it just now before uploading for them to use at the office and the file size is now 411! Did I hallucinate, dream and work simultaneously, see it wrong (my eyes are bad) ... or did compact/optimize cut the size in half? I doubt it.

I changed ExplodedPermutation to > 4 (I hope that was the right change, Mike). But my portal in Pickup works perfectly and instantly!

In fact, I'm going to add this same feature so staff can type part (interior) of product word and display all Contacts that have ordered it! If I wasn't so darned tired, I'm be on-the-ceiling excited!!

They are going to be tickled at work when they see this!! God, I love this business!!

LaRetta

[LaRetta]

Okay folks, I need to set something straight. I've been up since Saturday morning. And I may have read that file size wrong after adding Ender's Custom Function.

Because I compacted and optimized it just now before uploading for them to use at the office and the file size is now 411! Did I hallucinate, dream and work simultaneously, see it wrong (my eyes are bad) ... or did compact/optimize cut the size in half? I doubt it.

I changed ExplodedPermutation to > 4 (I hope that was the right change, Mike). But my portal in Pickup works perfectly and instantly!

In fact, I'm going to add this same feature so staff can type part (interior) of product word and display all Contacts that have ordered it! If I wasn't so darned tired, I'm be on-the-ceiling excited!!

They are going to be tickled at work when they see this!! God, I love this business!!

LaRetta

[Ender]

I'm glad it's working for you.

To test the change to the function, see if the key has lines with less than 4 letters omitted. You may also want to do a similar change to the ExplodedKey() function, as this is also used in the match field.

[Ender]

I'm glad it's working for you.

To test the change to the function, see if the key has lines with less than 4 letters omitted. You may also want to do a similar change to the ExplodedKey() function, as this is also used in the match field.

[Ender]

I'm glad it's working for you.

To test the change to the function, see if the key has lines with less than 4 letters omitted. You may also want to do a similar change to the ExplodedKey() function, as this is also used in the match field.