I have a BROWSE in Legacy on which I had effected Tagging, and it was working. I thought I would look into using the MARK attribute and in Properties named a queue field. Simply doing that apparently overroad my tagging, so I deleted the queue field. I have also deleted the MARK fields in the module’s queues and the field in the Window declaration. But I have not eliminated whatever underlying code is creating these effects.
Yes, it was working; I should have left well enough alone. But how can I eliminate the effects of have touched the MARKing attribute?
Any help is appreciated, even if you feel the need to call be a dummy.
Without seeing an example any suggestions on what uou might be missing are pure speculation.
Look at your LIST declaration in the “Window …” Button code editor. If it has a MARK(field) attribute then remove it.
Thanks for your reply, Carl.
I have removed that attribute, but it keeps coming back. It showed up when I entered a Queue field for MARK on the Properties sheet. Even though I have removed the entry on the Properties sheet, the code returns. This suggests that the entry initiated some template code that is not turned off by removing the entry.
I don’t think anything you have done with the Mark attribute and field would have broken your existing code. I’d start by updating the Mark attribute by removing whatever field you nominated.
Then have a look at your old code to see why it isn’t working.
In my experience the Clarion implementation of Mark is pretty useless and it is much better to use a separate queue of marked records.
1 Like