@KekuSemau is correct but let me a suggest a more efficient and manageable approach then using the adovbs constants file. METADATA allows you to define a reference to the DLLs constants even if your using Late Binding as is the case in a Classic ASP environment. It’s probably worth mentioning that you can add METADATA … Read more
For a text file, Data Source is the folder, not the file. The file is the table (SELECT * FROM ..). See http://www.connectionstrings.com/textfile
Common occurrence is likely you do not have adVarChar defined, so the CreateParameter() method is “improperly defined”. This is just an example of one of the many named constants found in the ADODB Library. A messy approach to dealing with this is to just define the value yourself something like; Const adVarChar = 200 The … Read more
follow http://support.microsoft.com/kb/896456 To start a 32-bit command prompt, follow these steps: * Click Start, click Run, type %windir%\SysWoW64\cmd.exe, and then click OK. Then type cscript vbscriptfile.vbs
I’ve added the Initial Catalog to your connection string. I’ve also abandonded the ADODB.Command syntax in favor of simply creating my own SQL statement and open the recordset on that variable. Hope this helps. Sub GetDataFromADO() ‘Declare variables’ Set objMyConn = New ADODB.Connection Set objMyRecordset = New ADODB.Recordset Dim strSQL As String ‘Open Connection’ objMyConn.ConnectionString … Read more
SQL injection attacks happen when user input is improperly encoded. Typically, the user input is some data the user sends with her query, i.e. values in the $_GET, $_POST, $_COOKIE, $_REQUEST, or $_SERVER arrays. However, user input can also come from a variety of other sources, like sockets, remote websites, files, etc.. Therefore, you should … Read more