jcolby at colbyconsulting.com
jcolby at colbyconsulting.com
Wed Jul 23 11:50:54 CDT 2003
Bonnie, Go for it. Code is easy, it just has to be taken one step at a time. Doing that will make you TRULY dangerous. ;-) John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Bonnie Snider Sent: Wednesday, July 23, 2003 12:34 PM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Continue Incrementing I know compared to you guys I'm a real novice. I've done a lot of databases and had to update a lot of fields, but I've always done it with update queries and macros. (I'm terrified of code and I don't understand what it means at all). But any time I've had to update a field based on an entry to a field in a record, I've always had to save the record before it would update. So in the properties of the field I would tell it to run a macro after update. The macro has a save record command and an open query command. The query is an update query. I know it's probably slower than code, but it works for me. >>> gustav at cactus.dk 7/23/2003 7:49:12 AM >>> Hi Virginia Well, if your form somehow is bound to table "DocumentList" and you use intMax = DMax(..., "DocumentList", ..) and this doesn't work, something else that prevents DocumentList from being updated must be going on. /gustav > I tried your suggestion and it didn't make any difference. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com Bonnie Snider, LAN Administrator DWS North Admin Phone: 526-9253 Cell: 430-1219 FAX: 526-9744 EMAIL: bsnider at utah.gov _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com