Re: Bug in ADO, SQL Server and latest OS SPs

I don't think Access uses Server Side Cursors be default.

Try this in an ADP:

Sub temp()
Debug.Print CurrentProject.Connection.CursorLocation =3D adUseServer
' shows False

' ------------
Debug.Print CurrentProject.Connection.CursorLocation =3D adUseClient
' shows True
' ------------

Is there something "non-defaultish" about the connection?
Debug.Print CurrentProject.BaseConnectionString

'PROVIDER=3DSQLOLEDB.1
;INTEGRATED SECURITY=3DSSPI
;PERSIST SECURITY INFO=3DFALSE
;INITIAL CATALOG=3DESOII
;DATA SOURCE=3DVOSTRO-DESKTOP\SQLEXPRESS

=2E.. Not that jumps out at me.

Of course, Microsoft might say that Access uses Server Side Cursors by
default.

As usual with Microsoft statements that means that there is a fifty
per cent chance that Access uses Server Side Cursors by default.

On May 12, 5:17=A0pm, "Tony Toews [MVP]" <tto...@[EMAIL PROTECTED]
> wrote:
> "Tony Toews [MVP]" <tto...@[EMAIL PROTECTED]
> wrote:
>
> >On a computer that is running Windows Vista, Windows Server 2008, or
> >Windows XP, an incorrect value is returned when an application queries
> >the identity column value of a newly inserted row in various versions
> >of SQL Server 2005 and of SQL Server 2000
> >http://sup****t.microsoft.com/kb/951937
>
> Comments indicate that this problem applies to client side cursors and
not=
 server
> side cursors. =A0Access apparently uses service side cursors by default.
=
=A0So this may
> not be a big deal at all.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> =A0 =A0Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> =A0 =A0Microsoft Access Links, Hints, Tips & Accounting Systems
athttp://w=
ww.granite.ab.ca/accsmstr.htm
> =A0 =A0Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/