Re: strange problem with sql
From: David Buchanan (dbuch328_at_cox.net)
Date: 01/26/05
- Next message: UncleSam89: "Re: Ramifications of running SQL Server 2000 and 2005 on the same"
- Previous message: Hugo Kornelis: "Re: Help with SP to check and add new user to database"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 26 Jan 2005 12:16:11 -0500
Eh... iirc, vb6 stores string literals in the executable file (spaces
between each letter)... maybe it has been tampered with? Try opening the
local executable and confirming that your queries are intact on those
machines...
"Joel H" <JoelH@discussions.microsoft.com> wrote in message
news:43B21281-59C4-4056-AE05-EA53E1F5CAC2@microsoft.com...
> This is a cross-post.. Some fellas in the microsoft.public.data.oledb
group
> gave me a clue. The difference in the character _ and W is just one bit.
>
> This problem has gotten worse. I now have 4 client computers that are
> getting the error. There are other letters that are getting
mistranslated:
>
> _ to W
> i to a
> o to k
> t to p
> o to g
>
> I found these bit pattern on the web (not sure how to translate myself)
and
> it appears that they are all different by one bit.
>
> Any further suggestions on what component is causing this will be
appreciated!
>
> Joel
>
>
> "Erland Sommarskog" wrote:
>
> > Joel H (JoelH@discussions.microsoft.com) writes:
> > > I have a vb6 app that is widely used in my organization that accesses
an
> > > sql 2000 db using ado/oledb. I am randomly getting errors from only
one
> > > computer (out of ~100). It appears that SQL Server is getting a
> > > different sql command than what my code is sending. My vb6 code looks
> > > similar to this:
> > >
> > > strSQL = "SELECT invoice_detail.date_added,... FROM invoice_detail
..."
> > > rsTemp.Open strSQL, g_Connection, adOpenKeyset, adLockReadOnly
> > >
> > > I get an error like this:
> > > Microsoft OLE DB Provider for SQL Server, Invalid column name
> > > 'invoiceWdetail'.
> > >
> > > The error doesn't always occur at the same place in my source code or
on
> > > the same sql statement. It does seem to most frequently replace
certain
> > > letters in table or column names with other letters. ie, it will
change
> > > "my_data_table" with "myWdataWtable".
> > >
> > > My first thought was that there was a virus or spyware program on the
> > > client workstation, so I had our support staff reformat and reinstall
> > > the os. That didn't help. My onlly guess now is that there is a
memory
> > > error. Any thoughts?
> >
> > The only thing I could think of is some character translation busniess
> > going on, but why it should attack an underscore is beyond me.
> >
> > Faulty memory is not impossible, but in such case one would execpt
> > other bad things on that machine, and most of all other characters
> > than _ to be mutilated as well. But I note that there is only one
> > bit that is different between _ and W.
> >
> > (I actually had such an error on my machine at home. I was running
> > with bad memory for six months before the error really started to
> > give me visible pronlems like random crashes. One funny incident was
> > that at one occassion the SQL Server executed was changed on one
> > single bit!)
> >
> > --
> > Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
> >
> > Books Online for SQL Server SP3 at
> > http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
> >
- Next message: UncleSam89: "Re: Ramifications of running SQL Server 2000 and 2005 on the same"
- Previous message: Hugo Kornelis: "Re: Help with SP to check and add new user to database"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
