Messages
Reply
Edit
Delete10:24 am
3PI0MBHLQ
| From: | Tuvia Vinitsky |
| To: | Thierry Nivelet (FoxInCloud) |
I have not been able to resolve this. I have grid level code and in http://west-wind.com/wwThreads/default.asp?Thread=3JV0QVEU2&MsgId=3K3002XPR
you said "'aw37' is the ID of the main container of the javascript grid - I confirm FAS has a bug here, will be fixed in next version to support grid-level events."
Was that fixed? I have the latest 1.265 version.
how does this new version go?
Is it quick for you to tell me what changed in the install in the last 3 days?
just sent you an update, hope it will fix your issue
otherwise please allow incoming HTTP requests on your dev machine so that I can test (see your WAN router / NAT doc if needed)
A few weeks ago you sent me new awgrd.dbf. It was working fine. Yesterday I installed the latest 1.26 from your ftp site over the 1.26 that was already there. Can't think of what else.
i might have an idea if you could remind what might have changed recently ...
Uh oh, sounds like I am the only one saying this. I do not have any public URLs, I can try and set one up asap. Do you have any ideas in the meantime?
any URL to test that?
The old problem I saw here is back in my latest versiin: click anywhere in any grid field and fic tries to run a form/class aw37. Does not matter whether gtid is dynmic or not. Simplest grid.
All grids in all my apps, about 200 all together, now do not work and produce this error.
First it seems wafterrowchange fires, then it looks for comething callsed aw37 as the click method, so we get from awajax
. . ..target form csannot be found
form 'aw36'
method or property: click