CFGRID strange behaviour in Production Server (Windows 2000 + ISS)

2011-08-11 Thread Luiz Milfont
Dear Sirs/Madams, I am facing a strange issue with CFGRID component, just in production server. In my development machine or any other, if I install Coldfusion8 and my application, it works just fine. I double-click a grid cell and edit its contents. Then I press the TAB key to move to the

Re: CFGRID strange behaviour in Production Server (Windows 2000 + ISS)

2011-08-11 Thread Steve 'Cutter' Blades
Have you checked that the prod server is running the same version of CF? Hotfix levels, all that? Steve 'Cutter' Blades Adobe Community Professional Adobe Certified Expert Advanced Macromedia ColdFusion MX 7 Developer http://blog.cutterscrossing.com Co-Author Learning Ext JS 3.2

Re: CFGRID strange behaviour in Production Server (Windows 2000 + ISS)

2011-08-11 Thread Luiz Milfont
Dear Steve, Yes, I´ve checked versions. All the same. I´ve applied all kinds of patches from Adobe site... I have even copied the CFIDE folder from my machine to production machine, thinking that it might be a CSS problem... Nothing has solved the problem yet. What I can say, if that maybe a

Re: CFGRID strange behaviour in Production Server (Windows 2000 + ISS)

2011-08-11 Thread Luiz Milfont
Could it be an EXT issue? Is there any way to update EXT on production server? I ask this, because my CFGRID component uses EXT. ~| Order the Adobe Coldfusion Anthology now!

Re: CFGRID strange behaviour in Production Server (Windows 2000 + ISS)

2011-08-11 Thread Steve 'Cutter' Blades
No, you can't update Ext on the server. You could write a straight Ext implementation, skipping the cfajax components all together. Or, it could be a data issue, where something in the data is breaking cfgrid's js. If you're server versions, hotfix levels, etc are all the same then it should

RE: CFGRID strange behaviour in Production Server (Windows 2000 + ISS)

2011-08-11 Thread Brook Davies
behaviour in Production Server (Windows 2000 + ISS) No, you can't update Ext on the server. You could write a straight Ext implementation, skipping the cfajax components all together. Or, it could be a data issue, where something in the data is breaking cfgrid's js. If you're server versions, hotfix