Too wierd... Access 2000, VB 6, and a "Drop Table"

Results 1 to 2 of 2

Thread: Too wierd... Access 2000, VB 6, and a "Drop Table"

  1. #1
    Jason Miller Guest

    Default Too wierd... Access 2000, VB 6, and a "Drop Table"

    My wierdometer is going off the scale with this one...<BR><BR>Visual Basic: Use a global connection object to hook into a database (as per Set objConn = CreateObject("ADODB.connection") ... objConn.Open <BR>"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & dbSource & ";User ID=admin;") then use a function to do nefarious bidding with that object (as per objConn.Execute(strSQL & ";")) and that&#039s it.<BR><BR>Issue: When using strSQL = "drop table [oddName_like-this]" the VB dies at me when it goes to execute. When I put the code together in VBScript, it works. When I set strSQL = "drop table normalName" the VB works.<BR><BR>ARGH Point: Anybody know why I can smite every table in every way *except* for the abnormal (user defined) tables in a mission-critical way?<BR><BR>[It&#039s not permissions; I&#039m the only person on my dev server.]<BR>

  2. #2
    Jason Miller Guest

    Default Must... have... more... Coffee!

    Okay, so it was permissions because I was also on my dev server. (I forgot to officially fillet a recordset before ignoring it.)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts