Cannot read property "allnames"

Classic Servoy
1

Hi,
We are using Servoy 5.2.4 and we have this issue randomly appearing: http://screencast.com/t/mnkwfAszWzH
It comes from this line:
vElements = forms[vForm].elements.allnames
Any idea why it might appear, randomly? The vForm is defined.
We also had this kind of random error with a specifc element name: http://screencast.com/t/4KE1TDZo
coming from:
forms[vFormName].elements.fld_organisationFilter.visible = true
Many thanks in advance for the answer.

2

Also a random error that appears on the form foundset: http://screencast.com/t/sAzExatXQb
coming from:
forms[vCurrentForm].foundset.getRecord(forms[vCurrentForm].foundset.getSelectedIndex())
when the vCurrentForm is defined.

3

I see those errors as well but it’s not reproducible, the code is correct and works 99% of the times I wasn’t able to figure out the cause so far. It only happens in client, never saw that in developer.

4

I only have those error messages in developer for several years.
It only happens (and not always) when changing and saving forms which are showing in smart client (started from developer).
In that case : restart the client and it’s fixed…

Regards,

5

Except the getRecord one, the others are also seen in the developer, and a restart of the debug client removes them.
But all of them are seen in the smart client, randomly.

6

please do upgrade to the latest 5.2.x or 6 to see if this is improved/fixed

It is very hard to say what goes wrong, do you have in the java console a bit more stack? So that we can see what the call exactly is?

elements should just always be there for a form.

7

I have this problem on 5.2.8 and 5.2.10.

8

I have seen the same thing in Developer. Usually when I restart the client after an error (any error) occurred. Most of the time it tells me that the property ‘elements’ doesn’t exists. As we all know this property is ALWAYS available on a form. So somehow things get in a weird state and requires me to restart Developer altogether to fix this.
This is all the way up to 5.2.11 (haven’t tried 6.x) on Mac OS X 10.7.2.

9

In my case it happens on servoy smart client running from servoy server in a production system, the users are quite annoyed by this. A simple logout/login and things get back to working fine.

10

ROCLASI:
I have seen the same thing in Developer. Usually when I restart the client after an error (any error) occurred. Most of the time it tells me that the property ‘elements’ doesn’t exists. As we all know this property is ALWAYS available on a form. So somehow things get in a weird state and requires me to restart Developer altogether to fix this.
This is all the way up to 5.2.11

+1

Happens in production environment as well.
Unfortunately it’s hard to get a reproducible situation.

11

developer is quite tricky
there some thing like this could happen, because of scripts running and stuff updating from the developer site,
in a developer you now and then could be in a wrong state that you have to restart anyway (like altering default values of form/global variables)

The problem is more how could these things happen in real smart or webclients

12

mihaela:
Except the getRecord one, the others are also seen in the developer, and a restart of the debug client removes them.

ROCLASI:
So somehow things get in a weird state and requires me to restart Developer altogether to fix this.

So when it happens in developer, it always happens (reproducible from there on), until you either restart the clients or developer is restarted.
When in happens in clients running on server, it always happens until you restart the client.

If you see this happening again in developer, please have a look in the log file to see if there is any error message/stack trace containing more info. Maybe a bit sooner then the actual ‘undefined’ error. There’s a case for this btw (SVY-1226).