John Bartow
john at winhaven.net
Fri Sep 24 17:23:26 CDT 2010
Spot on -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Friday, September 24, 2010 3:35 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Move children from one parent to another Arthur, I would think you might need a history of which factories the machines have been in, so just substituting a FactoryID in the machine record wouldn't be adequate. You need to add a record and perhaps have a date field to indicate when the machine was moved to that factory. Clients always think they don't want a history ... until they wake up one day and realize they do. Charlotte Foust On Fri, Sep 24, 2010 at 8:14 AM, Arthur Fuller <fuller.artful at gmail.com> wrote: > I have been asked to add a feature to an existing app and am trying to > think of a cool way to do it. The general idea is this: > > There are Factories.(PK FactoryID) > The Factories contain Machines (PK MachineID, FK FactoryID) > > On occasion, the client wants to move one or more machines to another > factory. Obviously the back-end stuff is simple: for each machine > selected, change the old FK to the new FK. > > My initial thought was a dialog that lists the machines in the > currently selected factory, allowing multiple-select; plus a list or > combo that lists the other factories owned by the client. Grab the PK > of the new Factory and walk through the selected Machines, changing the FK to match. > > Anybody got a slicker idea? > > TIA, > Arthur > -- > 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