NetTalk Central
NetTalk Web Server => Web Server - Ask For Help => Topic started by: agustinh2000 on June 20, 2019, 10:23:39 AM
-
Hi Bruce, I leave the modified accounts example with the refresh between browses in form_filter. It stopped working as of version NT 11.10
Attached Accounts (31).zip
Thank you!
Agustin
-
Confirmed!
Robert
-
The problem is that the parent procedure name, contains an underscore character.
ie
Filter_form
Change this to FilterForm and it works fine.
I'm not sure if this needs to be a rule forever, but at least for now "container" procedure names should not use an underscore...
cheers
Bruce
-
It works thank you!
-
Hallo Bruce!
We have some rule and all procedures have an underscore _
Is there another workaround?
Robert
-
Hi Robert,
>> Is there another workaround?
Unfortunately no. The "parent" system is getting quite complicated and unfortunately uses a _ as a procedure name separator.
Once you have underscores in your own names things go a bit pear-shaped.
Obviously it would be nice if I used some other character, but alas I did not think of that at the time, and so now the change would be a fairly substantial one (which would require time and testing-time I don't have available right now.)
In the future I hope to change this but I'm afraid in the short term the only workable approach is to remove underscores from "container" names.
Sorry
Bruce
-
Ok. Understand....but this sound like a big "bug" and why only now we know this?
(it was working some version earlier)
I have underscore in my procedures name for years.
For many reason I cannot rename procedures name...all procedures are involved in a complex security module and procedure names are stored and used for access. (not to mention hand code for this)
I will try to see what can I do but I'm really disappointed.
(This will cost me money and days/weeks to rebuild the concept and code)
Robert
-
Hi Robert,
>> Ok. Understand....but this sound like a big "bug" and why only now we know this?
because other bugs with screens refreshing have lead to some differences in the way that the "parent" is understood and parsed. the root of the change (on my side) is in the AlertParent method in netweb.clw. It may be possible for you to override that to adjust to your situation.
>> all procedures are involved in a complex security module and procedure names are stored and used for access.
It's possible you could extend your security template to store a "procedure name" of it's own. Default this to the current procedure name, then that leaves you free to change the actual procedure name.
Bear in mind that only "containers" are affected by this. So you don't need to change the whole app at this stage.
As I say, this _may_ change in an upcoming build - but I need to review all the places where parent is set, and constructed, and that's a non-trivial task. I don't have the time to do it right now, but possibly in the not too distant future. So I recommend against wholesale changes to your system, but rather focus on container procedures where events may not be propagating.
cheers
Bruce
-
Thank you Bruce! This make more sense ;-)
Appreciate!
Robert