RE: OLEDBDataReader has no rows, yet query is fine in Access
- From: v-yren@xxxxxxxxxxxxx ("Yuan Ren[MSFT]")
- Date: Fri, 16 Dec 2005 02:25:44 GMT
Hi Gary,
Welcome to MSDN newsgroup!
For your current issue, I think Brendan's suggestion is right! Access uses
the Jet SQL statement but ADO.NET just can recognize the ANSI SQL statement.
I suggest you watch "Comparison of Microsoft Jet SQL and ANSI SQL" article
in Microsoft Office Access Help. In "Major Differences" section, there is
some description as below:
=====================================================================
Microsoft Jet SQL supports both ANSI SQL wildcard characters and Microsoft
Jet-specific wildcard characters to use with the Like operator. The use of
the ANSI and Microsoft Jet wildcard characters is mutually exclusive. You
must use one set or the other and cannot mix them. The ANSI SQL wildcards
are only available when using Jet 4.X and the Microsoft OLE DB Provider for
Jet. If you try to use the ANSI SQL wildcards through Microsoft Access or
DAO, then they will be interpreted as literals. The opposite is true when
using the Microsoft OLE DB Provider for Jet and Jet 4.X.
Matching character Microsoft Jet SQL ANSI SQL
Any single character ? _
(underscore)
Zero or more characters * %
======================================================================
I hope this information helps. If anything is unclear, please let me know.
I look forward to your reply.
Regards,
Yuan Ren [MSFT]
Microsoft Online Support
.
- References:
- OLEDBDataReader has no rows, yet query is fine in Access
- From: Gary Bond
- OLEDBDataReader has no rows, yet query is fine in Access
- Prev by Date: Gridview Date formatting problem.
- Next by Date: RE: OLEDBDataReader has no rows, yet query is fine in Access
- Previous by thread: Re: OLEDBDataReader has no rows, yet query is fine in Access
- Next by thread: RE: OLEDBDataReader has no rows, yet query is fine in Access
- Index(es):
Relevant Pages
|