And when I test it on IE10, I get next exception:
Which is EXACTLY what my first post in this thread was talking about... that functionality has been blocked in modern browsers unless both elements are local and accessed on the same domain/IP, becuase it's a GAPING security hole anywhere else. The mere notion of passing the SQL login and password to client-side code is absurdly insecure even in the best of times.
LOL. And what should I do to make it work on every browser?
There's a reason things like database access is usually handled in SERVER-SIDE languages like PHP, ASP, PERL, PYTHON, RUBY, etc, etc...
I was a little shocked to see someone even trying to use ADODB via ActiveX in this day and age, but to be fair with 90% of the websites, tutorials and books in the topic of web development still having their heads firmly wedged up 1997's backside... it shouldn't have been that big a surprise.
Lemme put it this way, as my markup shows you should have a perfectly good FORM -- either ajax the submit, or just submit it normally to SERVER SIDE code for processing. Good rule of thumb, you start using INPUT without a FORM around it, you're probably doing something WRONG!
orld. RoW these things just don't even exist, for good reason! DirectX filters, ActiveX objects, behavior scripts (.htc), VML -- all proprietary IE stuff that isn't part of the W3C public specifications -- and again, for good reason. Insecure, unreliable, bloated, or just plain bad thinking that is why amongst experts IE over the past ten years has been the security equivalent of stripping naked, painting yourself in glow-in-the dark paint and running into the woods of North Vietnam in 1968 waving a spotlight screaming "shoot me, shoot me"
Edited by JasonKnight, 21 April 2013 - 05:27 PM.
The only thing about Dreamweaver that can be considered professional grade tools are the people promoting it's use.