[AccessD] Specify Startup Form

[Stuart McLachlan]

"column properties" such as "Lookup", "input mask" etc are user interface features, not table  
properties   and should not be in the BE. of a split datbase.

Actually,  "column Lookup" is a PITA. it should be left as Textbox to avoid all sorts of 
problems.


On 25 Mar 2022 at 12:04, Arthur Fuller wrote:

> Thanks, Jim.
> 
> A follow-up question: For a long time, I have defined
> column-properties such as Lookup in the FE, but gradually shifted to
> defining them in the BE -- the principal reason being that when
> creating forms, queries and reports in the FE, I "inherit" all that
> information automatically, rather than having to specify it each time.
> Opinions, one way or the other?
> 
> On Fri, Mar 25, 2022 at 11:41 AM Jim Dettman via AccessD <
> accessd at databaseadvisors.com> wrote:
> 
> >
> >
> >  BE is where they count, but some will define them in the BE, then
> >  import
> > to
> > the FE so when working with queries, you get the joins
> > automatically.
> >
> > Jim.
> >
> > -----Original Message-----
> > From: AccessD On Behalf Of Arthur Fuller
> > Sent: Friday, March 25, 2022 11:00 AM
> > To: Access Developers discussion and problem solving
> > <accessd at databaseadvisors.com>
> > Subject: [AccessD] Specify Startup Form
> >
> > I've forgotten how to do this. Can you remind me? (it's Access 10,
> > if that matters.
> >
> > --
> > Arthur
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> 
> 
> -- 
> Arthur
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>