[AccessD] Dang Bound Forms Again

Gustav, Mark, Jim and Charlotte:

Hoo boy!  Have I got egg on my face.

AllowAdditions property was set to False.  Which is okay unless the
recordset is empty.  Then you get the blank screen.

The User has to click the add button to set the property to true.

Sorry for the wild goose chase.

Sign me,

Red-Faced in Del Mar

----- Original Message ----- 
From: "Gustav Brock" <gustav at cactus.dk>
To: <accessd at databaseadvisors.com>
Sent: Thursday, June 05, 2003 12:21 AM
Subject: Re: [AccessD] Dang Bound Forms Again


> Hi Charlotte
>
> Instead of inventing a false condition you can just state it:
>
>   SELECT * FROM MyTable WHERE False
>
> /gustav
>
>
> > Oh, you mean nothing in the recordsource, not no records returned by it.
> > So don't remove the recordsource, replace it with one that returns an
> > empty recordset.  The way I do it is to use a standard recordsource that
> > returns no records (i.e., "SELECT * FROM MyTable WHERE 1 = 2").  That
> > allows your form to be bound to the fields in MyTable but since the
> > where condition is always false, it returns an empty recordset.  Then I
> > use code to set the recordsource to the appropriate one when something
> > triggers it such as a choice in a dropdown.
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>