View Single Post
  #4 (permalink)  
Old November 16th, 2004, 02:22 AM
mikersantiago mikersantiago is offline
Authorized User
 
Join Date: Sep 2004
Location: Las Pinas, , Philippines.
Posts: 11
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to mikersantiago
Default

Hi again Mat,

I understand the script you gave is the right/ more proper way to establish database connections (thus avoiding redundancy, database connectivity problems, etc.). I will adopt this. How about the establishing recordset part?

This script for access works fine,

set rsProdInfo = Server.CreateObject("ADODB.Recordset")
rsProdInfo.Open "products", Conn, adOpenStatic, adLockOptimistic, adCmdTable
'products - table
'Conn - database connection

Will this script work for SQL Server as well?
Does SQL Server understands the part,
rsProdInfo.Open "products", Conn, adOpenStatic, adLockOptimistic, adCmdTable


Does SQL Server has different ADO constants from Access database or ADO is universal for all databases using the ADO technology? (i.e. adOpenStatic, adLockOptimistic, etc.)

Are there good website/links that discusses different connections to SQL Server that you know (aside from the oledb - connection string you gave above, I just want to familiarize myself to the different connections)? Thanks a lot :)

Reply With Quote