Wednesday, March 21, 2012

Current Recordset does not support updating. This may be a limitation of the pro

I keep getting this error when I try to update

Current Recordset does not support updating. This may be a limitation of the provider, or of the selected locktype.

It worked fine in Access, but when I switched to SQL Server it stopped working.

Can someone help! Please!

thx

JustinHave you declared a primary key in SQL Server for the table(s) in your rowset?

-PatP|||Originally posted by Pat Phelan
Have you declared a primary key in SQL Server for the table(s) in your rowset?

-PatP

yes i have|||Is the column that SQL Server recognizes as the primary key included in your keyset? Can you post the DDL (the CREATE TABLE statement) and the DML (the SELECT statement) so we have some more to go on?

-PatP|||Originally posted by Pat Phelan
Is the column that SQL Server recognizes as the primary key included in your keyset? Can you post the DDL (the CREATE TABLE statement) and the DML (the SELECT statement) so we have some more to go on?

-PatP

Actually I found out what the problem was.

Access will allow 'ORDER BY' in the SQL statement, but SQL Server won't.

Thanks for your help though!

Justin|||Originally posted by justinbezanson
Actually I found out what the problem was.

Access will allow 'ORDER BY' in the SQL statement, but SQL Server won't.

Thanks for your help though!

Justin

What do you mean by "SQL Server won't"?
[Order By] is a commonly used in SQL Server. Somthing else must be the cause of the problem and I doubt that it is [Order By].|||Originally posted by GDMI
What do you mean by "SQL Server won't"?
[Order By] is a commonly used in SQL Server. Somthing else must be the cause of the problem and I doubt that it is [Order By]. I had some trouble swallowing that one too, but as long as Justin is happy with his answer, I'm Ok with it. I use ORDER BY all of the time, and have never had any problem with it, even in Recordsets.

-PatP

No comments:

Post a Comment