[AccessD] Access crashes when assigning empty recordset

[Fred Hooper]

Thanks for the suggestion. Unfortunately if I comment out the line that
sets the recordset to nothing it still crashes.

So I tried changing the value on the server with a stored procedure and
used well-tested “refresh” code (it has to be refreshed by executing a SP;
Access can’t Refresh an ADO recordset). That failed too. Finally I changed
the value, closed and reopened the form — which worked.

I guess I’m in some form of never never land. But it’s so fast; I’m getting
5 ms form fill and refresh times.

The refresh approach (and code) that failed works perfectly for subforms;
this was my first use of it for a main form. Happily, there isn’t another
form like this one, so I’ll probably keep the close/open kludge.

My memory is that you wrote something about disconnected recordsets, it was
part of getting me started on this approach — for which I also thank you.

On Tue, Sep 11, 2018 at 9:15 PM Charlotte Foust <charlotte.foust at gmail.com>
wrote:

> I suppose it might be possible that setting the frm.recordset to nothing
> leaves you in a state where you cannot assign a recordset to it.  What
> happens if you comment out that line?  Does it give you the same error or a
> different one?  And what is the error?  Honestly, I can't recall every
> trying to set a subform's recordset.
>
>
> Charlotte Foust
> (916) 206-4336
>
>