From: iccsi on
I use recordcount to check my DAO.recordset is empty or not.
The recordcount returns 1 when the resordset is empty.

Are there any work around for this?

Your help is great appreciated,
From: Dirk Goldgar on
"iccsi" <inungh(a)gmail.com> wrote in message
news:80308099-9f06-42c9-bbc7-9f9f57948450(a)h21g2000vba.googlegroups.com...
>I use recordcount to check my DAO.recordset is empty or not.
> The recordcount returns 1 when the resordset is empty.
>
> Are there any work around for this?


I've never heard of such a thing, and doubt your results. Please post your
code.

--
Dirk Goldgar, MS Access MVP
Access tips: www.datagnostics.com/tips.html

(please reply to the newsgroup)

From: iccsi on
On Apr 20, 11:23 am, "Dirk Goldgar"
<d...(a)NOdataSPAMgnostics.com.invalid> wrote:
> "iccsi" <inu...(a)gmail.com> wrote in message
>
> news:80308099-9f06-42c9-bbc7-9f9f57948450(a)h21g2000vba.googlegroups.com...
>
> >I use recordcount to check my DAO.recordset is empty or not.
> > The recordcount returns 1 when the resordset is empty.
>
> > Are there any work around for this?
>
> I've never heard of such a thing, and doubt your results.  Please post your
> code.
>
> --
> Dirk Goldgar, MS Access MVP
> Access tips:www.datagnostics.com/tips.html
>
> (please reply to the newsgroup)

Thanks for the message,
Yes, there is a bug in the query.
Thanks again,