"kgs" <st****@tlen.pl> wrote
Problem exists on ms-access, ms-sqlserver
using ADO (not in ODBC), visual Basic, C#,
and VB.NET.
Somethimes when I open second recordset
in this same connection that first, it has EOF,
but I know, that there are records. There aren't
error when I put Sleep 500, before opening,
or I open from second connection.
I do not believe there is a Sleep 500 statement in VBA, I conclude this is
an ADO problem. As I believe ADO.NET is normally used with C# and VB.NET, it
may not even be a problem with the classic ADO used with Access.
I have only used ADO in the Access environment, and I have to say that I was
unimpressed with its intuitiveness and ease of use (which I thought was less
than DAO), as well as the performance (which was OK, but not the "blindingly
fast" that some proponents have hyped.
In any case, my guess is that the delay is something in the network, or the
server, or in Microsoft SQL Server itself. However, if your half-second
Sleep seems to consistently work around the problem, it would also not
appear to be "pressing" or "urgent".
It also would seem you have done enough homework to be able to reproduce the
problem, and if you feel it is a defect, I suggest you report it to
Microsoft tech support -- there is no charge when you report a defect, and I
believe, if you ask, you can determine that before being charged for the
incident.
Good luck with your posting in comp.databases -- they are sometimes a little
touchy there about items dealing with specific databases. You may notice
that I deleted that newsgroup from this reply.
Larry Linson
Microsoft Access MVP
