Trapping "no current record"

julietbrown

New member
Local time
Today, 03:16
Joined
Aug 23, 2004
Messages
9
I know how to do this IF the reason there's no current rec is because I am at EOF or BOF, but the problem is if a record has just been DELETED. The recordset clone isn't "empty" and we are not at the end of it, but if you refer to the record code crashes. :confused:

The currentRecord property returns a number that is the record number. "Help" doesn't help me discover anything about the value of this number when there's no current record ... is it -1 or something?
 
Whats the code you are using?
Is the form bound?
Are you using ADO? (is there a status for the record, I know there is a recordset status...)


Vince
 
Thanks, and thoughts

Yes, the form is bound to a query.
Actually, on my way to work I suddenly thought I may be able to get round this by requerying the form immediately after the Delete record op.
But I'm interested in 'recordset status': I think I've looked at this (several times) in my quest for a solution to this problem, but will look again. (The recordset I'm using in the code is a clone of the form recordset.)
 

Users who are viewing this thread

Back
Top Bottom