XPost: microsoft.public.sqlserver.programming   
   From: genew@ocis.net   
      
   On Tue, 31 Jul 2012 14:25:12 -0400, "Bob Barrows"   
    wrote:   
      
   >Gene Wirchenko wrote:   
   >   
   >>   4) I would like to avoid using ActiveX to communicate between the   
   >> Web page and SQL Server and preferably without having to add more   
   >> software to the server.  Otherwise, my app is going to be limited to   
   >> IE.   
   >The only time scripting language will restrict you to IE is if you use   
   >vbscript in client-side code.   
   >   
   >There are no such restrictions in server-side code: the language being used   
   >in the server-side code to generate html to be sent to the browser is   
   >completely browser-independent. The html that is generated is what can limit   
   >the browser being used. Browser-restricted html can be created by any   
   >scripting language.   
   >   
   >So, depending on what you mean by "ActiveX"  (are you talking about ADO, or   
   >perhaps ADO.Net? ), its use or avoidance will not have an effect on what   
   >browsers can be used. Even if you are planning to directly access the   
   >database from the client-side code (which can really only work in a WAN   
   >environment) it is certainly possible to use ADO in javascript, which is   
   >browser-independent.   
      
        My understanding is that in order to access the data with the   
   browser, I have to create an ADODB.Connection object and an   
   ADODB.Recordset object using ActiveXObject() which Firefox (for   
   example) does not have.  If there is another way of doing it, I would   
   be delighted to find out how.   
      
   Sincerely,   
      
   Gene Wirchenko   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)