Martin Reid
mwp.reid at qub.ac.uk
Sun Mar 19 10:18:53 CST 2006
Rocky Would you not create the Job first and then the equipment required to do the job? Martin Martin WP Reid Training and Assessment Unit Riddle Hall Belfast tel: 02890 974477 ________________________________ From: accessd-bounces at databaseadvisors.com on behalf of Rocky Smolin - Beach Access Software Sent: Sun 19/03/2006 15:25 To: Access Developers discussion and problem solving Subject: [AccessD] MAny-To-May Dear List: This is a preventive maintenance application. There is a table of Jobs and a table of Equipment. Since one job can do many equipments and one equipment can be called out in many jobs there is a table that sits between them - tblJobsEquipment which has the PK from tblJobs and the PK from tblEquipment as FKs. The equipment table is relatively static. The job table changes all the time. On the form where jobs are created and maintained, the user selects the equipment from a combo box. The jobs for that equipment are then displayed in a sub-form. The problem comes when trying to create a new job. Since there's no PK yet for the job I get an error "cannot create record; join key (to the JobEquipment table) is not in the recordset. Indeed if I put a debug statement in the BeforeInsert event of the sub-form the PK of the Jobs table is still null. How does one work around this problem? MTIA Rocky -- Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com