Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server CE / July 2008

Tip: Looking for answers? Try searching our database.

OleError 0x80040E05 - Object was open during Recordset.Open for certain tables

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ender - 10 Jul 2008 18:47 GMT
Hello, all.

I think it is better place to post, instead of *.data.ado. Sorry for
multiposting.

Last four hours I fought with very strange error. When I try to open a table
through simple query (select * from TableName) ADO (OLEDB) gives to me
abovementioned error message. Some tables are opened without a problem but
for some tables there is error. I tried to determine what is the difference
between these tables and was very surprised. This error happens when table
have nvarchar fields with maximum length more than 127. For example this
table will be opened without problems:

For this table opening works

create table Projects(
 ID integer identity (0, 1) constraint PK_Projects primary key,
 Name nvarchar (127) not null);

but this table won't open

For this table opening doesn't work

create table Projects(
 ID integer identity (0, 1) constraint PK_Projects primary key,
 Name nvarchar (255) not null);

Both tables perfectly opened through Visual Studio 2008. I suppose it uses
ADO.NET but I use ADO (OLEDB) from program written on Delphi. Could someone
direct me to the place in the documentation where such restriction is
mentioned? Andy why such non-informative error message?
Ginny Caughey MVP - 10 Jul 2008 19:14 GMT
Ender,

This is a known bug/limitation in the OleDb provider, but I don't know that
it's documented anywhere.

Ginny Caughey
Device Application Development MVP

> Hello, all.
>
[quoted text clipped - 30 lines]
> direct me to the place in the documentation where such restriction is
> mentioned? Andy why such non-informative error message?
Ender - 10 Jul 2008 19:34 GMT
> This is a known bug/limitation in the OleDb provider, but I don't know
> that it's documented anywhere.

Oh, thanks. At least someone indicated that this is a bug of the Microsoft's
software. I worried that the bug in my code. Such a pity, almost half or
work day is lost. :-(
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.