Product documentation incorrectly stated '?' is the preferred parameter marker. (Bug #37349)
There was a high level of contention in the connection pooling code that could lead to delays when opening connections and submitting queries. The connection pooling code has been modified to try and limit the effects of the contention issue. (Bug #34001)
An incorrect value for a bit field would returned in a multi-row
query if a preceding value for the field returned
When using the
profile details and then reading back saved data would result in
the default values being returned instead of the updated values.
method was not implemented.
GEOMETRY field types would return
an unknown data type exception.
When creating a connection, setting the
ConnectionString property of
would throw an exception.
When using encrypted passwords, the
GetPassword() function would return the wrong
An error would be raised when calling
GetPassword() with a
When retrieving data where a field has been identified as
containing a GUID value, the incorrect value would be returned
when a previous row contained a
for that field.
SqlDataSource to open a
connection, the connection would not automatically be closed
when access had completed.
When creating a new stored procedures, the new parameter code
which permits the use of the
@ symbol would
interfere with the specification of a
TableAdapter Wizard would fail when
generating commands that used stored procedures due to the
change in supported parameter characters.
TableAdapter wizard in combination
with a suitable
only the associated
statement would also be created, rather than the required
Fixed profile provider that would throw an exception if you were updating a profile that already existed.
Fixed problem in datagrid code related to creating a new table. This problem may have been introduced with .NET 2.0 SP1.