[AccessD] Split form wizard

Tony Septav TSeptav at Uniserve.com
Wed Nov 19 16:28:47 CST 2014


Hey Stuart
Good stuff. As I mentioned I have not replied to the concerns on the list
for ages. It was kind of fun.  Anyway got to fade into the background again.
All the Best to those of you that are still prospering with your Access
ventures.

Tony Septav
Nanaimo, BC
Canada

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: November-19-14 4:07 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Split form wizard

One other "wrinkle"  if you haven't done it already:

I start with an unbound form and place a narrow continuous form on the left
hand side with 
basic info such as the persons name - in your case it may be the naimal ID. 

Then I put the tab control beside it with all the appropriate sub forms on
various pages.

I create a hidden text control on the main unbound form with a ControlSource
something like:
=[frmEmployeeList].[Form]![EmployeePK]

Then I put that  control's name in  the "Link Master Fields" of the
subforms.

That way users can see/sort/filter a list of the subjects and click on any
one to see all of that 
subject's info.

-- 
Stuart

On 19 Nov 2014 at 12:59, Susan Harkins wrote:

> Charlotte, it's working nicely and what's really nice about the whole
> arrangement is that I can easily add more pages and quickly drop a
> subform. I kind of see that happening. :)
> 
> Thanks for the direction everyone -- it's a good choice. And you're
> all right -- it was amazingly fast and simple.
> 
> Susan H.
> 
> On Wed, Nov 19, 2014 at 12:22 PM, Charlotte Foust
> <charlotte.foust at gmail.com > wrote:
> 
> > Susan,
> >
> > There are lots of tricks to keeping subforms in sync on tabs, and it
> > simplifies the whole process rather than complicating it.  You can
> > present a clean, intuitive interface where the use can see the
> > categories available to them and quickly find what they're looking
> > for without being overloaded with information at any one time.  All
> > the parent form needs to do is hold the primary keys you need to
> > link the subforms.  Your queries for the subforms are simplified
> > because they don't need to include multiple tables to get the right
> > records.
> >
> > Charlotte
> >
> >
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8596 - Release Date: 11/19/14



More information about the AccessD mailing list