A Field by any other name...

[RossG]

I have a number of scrolling list fields
ListField1 to ListField4.

This worked until recently when I got an
error on a line which put values into ListField1
claiming that there was no such object.

After a change of field name the problem stopped -
for a while - then started again at the same line.

Sometimes this error arises even after the first
cycle has put info into the field - then fails to recognize it
on the second cycle.

Have I done something silly (again)?
Have I contravened the the naming rules
(to which I can't find a reference)?
Am I expecting too much from LC7.1.4?

[LiveCode_Panos]

Hi RossG,

Just wondering, are those 4 fields on the same card?

Best,
Panos
--

[dunbarx]

Hi.

Certainly no naming conflict exists.

Panos asked an important question, since the error generally indicates that the engine cannot find the object, not necessarily that the object does not exist at all, but might be somewhere else temporarily.

So check that no handler locks the screen and navigates somewhere else, as he suggested. Perhaps search for all screen locking lines of code, comment them out, and step through whatever handler is causing the issue. See if you moved.

Craig

[RossG]

Fixed this problem but not sure how.

I removed all the lock/unlock screens and
replaced only one or two which were
necessary for view comfort. Also made
a few minor changes so who knows?

Still, hard to believe that LC can't find a field.

[dunbarx]

Hmmm

Well, it is either operator malfunction or gremlins, Both have happened to me.

Craig

[SparkOut]

Did you use the variable watcher when testing? I don't know what versions apply but I have hit a bug where the VW caused that error in v 9.0 dp1 on Windows 10