I have the same problem, but it happens with the non Unicode version of
SQLDriverConnect(). The code has been heavily used on WinXP and Win2K
servers for a couple years. So far, on 3 or 4 Win2K3 server, it will crash
infrequently during this ODBC call. The only thing I get is a standard
popup that says something like "something at 0x7f3f2d24 tried to access blah
blah and is invalid". Pressing cancel does not allow the application to be
debugged - the stack is just too trashed.. Doesn't help to be running in
..Net 2003 debugger either as the call stack is hosed and the memory location
that it breaks at is invalid.
Can anyone help me? Is there something strange about Win2K3 Server and SQL
Server on the same machine.
[quoted text, click to view] "JUNK" <bhemachandran@wyse.com> wrote in message
news:%23nU4bXhhFHA.3608@TK2MSFTNGP12.phx.gbl...
>I tried to connect to a local SQL server database using SQLDriverConnect in
>a VC++ project, on a Windows 2003 OS. It is an unicode project. Everytime
>the code reaches SQLDriverConnect it crashes. try catch block did not work.
> I tried to pick up some samples from websites and found that none of the
> website did give me samples of unicode project to interact with SQL server
> database.
> My code fails only in Windows 2003 OS, but the same code works in XP.
> When I implement the code in win32 application (not unicode) in Windows
> 2003 OS it works fine.
>
> Can anyone help me?
>