John Colby
jcolby at colbyconsulting.com
Fri Sep 5 16:33:36 CDT 2003
because the form goes back to the first record. :-( John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Mike and Doris Manning Sent: Friday, September 05, 2003 3:20 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Record deleted by user So why not have the FORM requery itself after the delete check box code finishes processing? Doris Manning Database Administrator Hargrove Inc. www.hargroveinc.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby Sent: Friday, September 05, 2003 2:07 PM To: AccessD Subject: [AccessD] Record deleted by user I am trying to implement a "selected flag" system for a particular form. I create a table local to the FE with two fields: SelectedID Long Selected Boolean I modify the form's query to do an outer join between the pk of the original table and SelectedID. I add a check box to the form bound to the Selected field. Whenever the user clicks the check box a record is created in the new table, the SelectedID is set to the PK of the original table and the Selected field is set true. All fine so far. Printing works fine - filter on records with a join to this table and selected = true. The odd behavior comes if I delete the records in the new Selected table. If I build a query that displays the original table joined to the Selected table, when I delete any records in the Selected table, the fields in the query from the Selected table display the words "Deleted" and I can no longer enter any data in that field because I get a JET error "record deleted by user". I have to requery the query and then I can again create new records. This is an issue because the FORM's recordset works until I delete a record in the selected table, then the checkbox FOR THAT RECORD ceases to work for no apparent reason. The reason of course is this problem discussed above. John W. Colby www.colbyconsulting.com _______________________________________________ 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