Field Palette

[jlockley]

I have just discovered the field palette, which I used to add a few temporary fields to a form for the purpose of filtering.

However: Content of fields added with the help of the field palette move independently of the rest of the records. I'd love to know why. (If I have STATE selected, for instance, while viewing John Jones's record and move to the next record, the state entries will come from the following records, but all of the rest of the data will be in Jones' record.....

Question 2: The field palette remains active even after exiting design mode. It would be nice to know why..as in what purpose would it serve outside of design mode. This is granted along the lines of why is the sky blue or what purpose do flies serve, but I am curious.

 

[footpad]

jlockley,

I'm not really following #1 at all. The data in a field object should be consistent, regardless of how the field object was added. Data from different records can be symptom of a corrupted table, but that's not always the problem. You might verify the table.

Barring that, I would check the data model and see if there's any code reasons why you wouldn't be seeing the correct record. If there's no code and the relationships are properly defined in the data model, there's no reason (other than corruption) for this kind of problem.

Also, if the table verifies and the problem persists, try recreating the linking indexes. I have see cases where those will get damaged.
As far as question #2 goes, I don't really know, though I suspect that the field palette was a) written in Delphi and b) written quickly. There is no logical reason for it to continue to appear after you run the form. However, it's not really a part of the form designer. The FP is a separate (non-modal window) and it's clear that the form designed doesn't tell it to go away. Not much we can do about that.

Hope this helps...

-- Lance

 

[jlockley]

Thanks. I am really curious rather in dire need of help (as opposed to the usual situation). Just for information, there is only one table in the data model. It's so very odd. The purpose for which I need it (Identifying records to exclude from a set) works just fine. It's just odd.