Browsetable SQL Server 2000

I have a tough question (well tough for me). We're noticing that for 2
of our users out of the 75 that use the system, the tracer shows that
the Set No BrowseTable On command is being passed for these two and
it's causing a host of issues with their account in our application.
They aren't able to retrieve correct Primary keys for a row they just
updated or inserted.
I've read this has something to do with client side cursors in ASP, but
I dont know a work around.
The authentication is NT Authentication if that matters.
ThanksCheck out ODBC SQLSetStmtOptions. The SET NOBROWSETABLE and FOR BROWSE
options are for Meta Data handling. They can cause additional work and
network traffic; however, some usage is required in order to do parameter
validation and statement parsing.
You should be able to set these options through ADO, most likely at the
Recordset object level.
Check out this link for ODBC:
http://msdn.microsoft.com/library/e...asp?frame=true
Sincerely,
Anthony Thomas
"belacyrf" <bela@.webnet-x.com> wrote in message
news:1104859698.178707.185530@.c13g2000cwb.googlegroups.com...
I have a tough question (well tough for me). We're noticing that for 2
of our users out of the 75 that use the system, the tracer shows that
the Set No BrowseTable On command is being passed for these two and
it's causing a host of issues with their account in our application.
They aren't able to retrieve correct Primary keys for a row they just
updated or inserted.
I've read this has something to do with client side cursors in ASP, but
I dont know a work around.
The authentication is NT Authentication if that matters.
Thanks