Still Struggling

[Graham Wickens]

1) If I have ANY filters at all, the problem of "unable to add key to tag" returns, even on queries!

2) I have been merging different files together into one main file. I have lookup tables assigned to most fields in the new master file, allowing updates and additions. I have been working through the file adding to/updating the lookup files. When I come to an entry that is not on the lookup file I press "ctrl-C" to copy to the clickboard, click on "enter" on the lookup table and then "Ctrl-V" to try and copy the entry to the lookup table additions form. Nothing happens, Ctrl-V & Ctrl-C are not recognised at this point. Is this correct? and how do I get around it (apart from re-typing every new entry)?

3) Can someone help me get started with action scripts with the know-how on the following:
if "operator" field is blank then set op-unique to blank.
if "w_o_date" (8 chars) not blank the set "C3" to "W".
if "identity" is blank then set "identity" to "-canx-"

I can get all this to work on new records by setting up the above using default settings, but when I update a current record the defaults dont work. :(

Its not as if I am starting from scratch, I have all the above working just fine with Alpha 4 V6, which at the moment seems to me to be a more stable product than Alpha 5V4.

[Selwyn Rabins]

RE: Still Struggling

1. can you attach sample files to a message that demo how you can get an "unable to add key to tag" error by including filters in the index. i would be most interested in seeing this.

2. i cannot repeat any problem using control V while doing data entry into a lookup table. I did this: went to the sample invoice app that ships with a5. opened "invoice" form. copied a comany name to the clipboard with ctrol-c. then entered a new invoice. that caused the customer_id lookup window to open. clicked the "Enter" button to enter a new customer id. this opened the customer form. gave focus to the company name field and pressed control-V to paste. it worked fine. if your scenario is different, please include specific instructions on how to repeat.

3. default values in field rules are only MEANT to work during data entry. not during edits of a previously saved record. if you want to define rules that apply to editing of exisitng records then you need to be more specific. should the default value be entered into the field regardless, or only if there is no current entry in the field (for example). if the value is to be entered into the field regardless, then it is really a calc field that you are defining, and you can certainly define this in field rules.

if on the other hand, the "default" value is intended to be entered into the field when the field gets focus, if there was no previous value in the field, and the user is still allowed to overwrite it, then it is easiest to do this by defining scripts attached to events on forms.

for example, to do your first rule: if operator is blank then set op-uinque to blank, you could do several things.
a) you could define a script for the onDepart event for "operator":

if operator.text = "" then
op-unique.text = ""
end if

b) you could define a script for the onInit event for op-unique, (same as above script)

c) if you did not want to overwrite an existing value in op-unique, then:

if operator.text = "" .and. op-unique.text "" then
op-unique.text = ""
end if

[Graham Wickens]

RE: Still Struggling

Thanks for that Selwyn, I managed to get the third example working. The other two failed to work, I suspect because they are posted during lookup table processing and I dont know where in the action sequence the posting takes place.
Anyhow I have scaled-down the number of entries so as to fit the attached zip file into under 1Mb.

[Graham Wickens]

RE: Still Struggling

He is an example pf the type of filter expression that has been causing "heap lock errors" and "unable to add key to tag" messages.

Index name: Tidy_Up
Order: operator
Filter: (isnotblank("operator").and.operator"corporate").and.isblank("operator")

[Rich Drabik]

RE: Still Struggling

Graham,

Your filter expression is contradicting itself in that it is requiring the field to be blank and not blank at the same time. Maybe that last .and. should be replaced with an .or.:

(isnotblank("operator").and.operator"corporate").OR.isblank("operator")

Now the expression sets the following 2 conditions--

1. Operator contains an entry that can only equal "corporate"

OR

2. Operator is blank

If Operator contains anything other than "corporate", the record should be ignored.

Is this what you are trying to get?

[Graham Wickens]

RE: Still Struggling

Doh!

the filter should read:

(isnotblank("operator").and.operator"corporate").and.isblank("op_unique")

[Rich Drabik]

RE: Still Struggling

Doh! as well. I reread my explanation and realized I was thinking ="corporate" not "corporate", so the explanation doesn't make sense.