J Gould
gould.j at earthlink.net
Wed Apr 6 08:09:12 CDT 2005
IF the subform were also based on a query then why hide it at all. The data changes based on the table selected in the query. The query here is what would change, the subform would simply bring up data based on it. The trick is to have the PK the same in all tables ... an autonumber field that basically means nothing to anyone but the database. Good luck with it ! John Gould -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Erbach Sent: Wednesday, April 06, 2005 8:09 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Home inventory problem John, This is more like it! No, you're not too late. I'm just surrounded by San Francisco flower children in a marijuana haze! I'm not sure how similar the bits of data are that my friend is recording. I suppose that your method could also, quite simply, hide one subform and show another. Thanks, Steve Erbach On Apr 6, 2005 6:29 AM, J Gould <gould.j at earthlink.net> wrote: > Steve, > > I may be a bit late on this, but if the fields for his collections are > basically the same, then use a master form that is not tied to any > particular database. Then use SQL to populate a view form. I did this with a > program several years ago where we had two databases of programs that were > being run on a mainframe. It tracked the ownership, description of what the > programs did, when the programs were run and other details. It takes a bit > of work, but it eliminates a ton of redundant programming for each tab (in > this case). The main form is like a switchboard that the user would select > the table they want to see. The view form is then loaded based on sql from a > hidden field on the switchboard. What's nice about doing this, is once you > have the basics down on it, its very easy to create a search form that > allows you to filter the records returned on the view form. Also, then one > or two reports are all that's needed based again on the sql used to display > the view form. Although the initial programming may take a bit longer, you > save a ton of time by not having to reinvent the wheel at every turn. > > Hth > > John Gould -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com