Re: NoCurrent record error when calling ReQuery on a subform
- From: "kingston via AccessMonster.com" <u27511@uwe>
- Date: Tue, 24 Oct 2006 14:43:07 GMT
Put a debug stop just before that line and run the code. Check the number of
records in rs by entering the commands:
rs.movelast
rs.recordcount
I think that there will be no records in rs. Therefore the error message is
correct. Since you use an OR in your conditional, it's as good as useless
(the record counter is always going to be something other than .EOF OR .BOF)
Anja wrote:
I don't think that this conditional is working the way you want it to:[quoted text clipped - 48 lines]
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-modules/200610/1
Hi,
Thanks for the reply. The recordset is definitely there. It works fine
normally... only when I call ReQuery after the tab change event
happens, that is fails.
The error happens on the line:
MsgBox rs![FormalName]
Thanks,
Anja
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-modules/200610/1
.
- References:
- NoCurrent record error when calling ReQuery on a subform
- From: Anja
- Re: NoCurrent record error when calling ReQuery on a subform
- From: kingston via AccessMonster.com
- Re: NoCurrent record error when calling ReQuery on a subform
- From: Anja
- NoCurrent record error when calling ReQuery on a subform
- Prev by Date: Re: NoCurrent record error when calling ReQuery on a subform
- Next by Date: Re: OpenRecordset from query
- Previous by thread: Re: NoCurrent record error when calling ReQuery on a subform
- Next by thread: Re: DCount not giving expected result
- Index(es):
Relevant Pages
|