|
|
Posted by Neil on 05/17/05 00:33
"Bri" <not@here.com> wrote in message
news:LP5ie.1374026$Xk.296760@pd7tw3no...
> Neil wrote:
>
>> (Wait! A brainstorm: the form is initial unbound. (I removed the
>> recordsource from the form, since the recordsource is going to be set in
>> the Form_Open event anyway. Why have the data be initially loaded only to
>> be immediately replaced with new data?) When I specified the main view
>> that I use as the recordsource in the form's recordsource property, the
>> form works fine when initially loaded, even with only one call to
>> SetRecordSource(). So apparently, one setting of the recordsource was
>> necessary to change the form from being unbound to bound, and another is
>> necessary to get it to work correctly as a bound form. Still doesn't
>> explain *why* that would be the case; but at least it's starting to make
>> a little sense.)
>
> It could be that in the unbound state there is something 'waiting' that
> times out eventually?
Not sure what you mean. In it's previous, unbound state, the form was opened
and immediately populated via the Form_Open event (using default values for
the options). Not sure what would time out.
>
> In any case, when I do similar things to this, rather than leave the form
> as unbound initially, I set the recordsource to the main recordsource but
> with a where clause that forces no records to be returned (eg WHERE
> myIdentityField=0). This gives you an empty recordset that has all the
> fields in it. This also eliminates the initial form displaying #NAME# in
> the controls.
Right, that's a good idea.
Neil
>
> --
> Bri
>
Navigation:
[Reply to this message]
|