Thanks for the report! I tried this out and was able to reproduce the same
behavior. I've submitted a bug.
--
Brannon Jones
Developer - MDAC
This posting is provided "as is" with no warranties and confers no rights.

"Martin J. Evans" <anonymous@discussions.microsoft.com> wrote in message
news:0b2901c39729$fd7c2210$a501280a@phx.gbl...
> Anyone seen this before:
>
> Using MS SQL Server ODBC driver version 3000.81.9030.04.
> Create a table and deny select permission to a specific user
> From odbctest do a full connect with ODBC 2.0 checked
> Do an SQLPrepare(select * from table)
> Do an SQLNumResultCols - this fails with permission denied
> DO an SQLExecute and you get an exception in odbctest
>
> "The instruction at "0x119c8fcc" referenced memory at
> "0x0170e000". The memory could not be written"
>
> Better exception data from my own application instead of
> odbctest says:
>
> Exception Address: 0X1F9C8F22
> Number of Parameters: 2
> Exception Record: 0X00000000
> Exception Information (RW Flag) : Write
> Exception Information (Virtual Address) : 0X0162E000
>
> Module: C:\WINNT\System32\SQLSRV32.dll, Section: 01,
> Offset:00007F22
> Call Stack:
> Address Frame
> 1F9C8F22 0120F854 SQLNumResultCols+3EB
> 1F9EF7E4 0120F8B8 BCP_init+5D2
> 1F9F1737 0120F8CC SQLNativeSqlW+637
> 1F9F47DA 0120F900 SQLExecute+1E1
> 1F7CD793 0120F91C SQLExecute+D1
> 004227CC 0120F988 0001:000217CC
> C:\WINNT\System32\esoobserver.exe
> 00419A85 0120FF84 0001:00018A85
> C:\WINNT\System32\esoobserver.exe
> 0042F218 0120FFB8 0001:0002E218
> C:\WINNT\System32\esoobserver.exe
> 77F04EDE 0120FFEC lstrcmpiW+BE
> No deeper stack frame
>
> Martin

Brannon Jones [MS] wrote:
> Thanks for the report! I tried this out and was able to reproduce the same
> behavior. I've submitted a bug.

Good.

Thank you.

Martin