jwcolby
jwcolby at colbyconsulting.com
Mon Sep 24 13:04:13 CDT 2007
Ahh, love those educational experiences. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte Sent: Monday, September 24, 2007 1:54 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Leave Subform I did thanks... I had to use a number of approaches including setting a variable ON EXIT that was evaluated in the BEFORE UPDATE to determine if the user was moving from record to record...or leaving the subform.. To track down exactly where I need each piece of code: I had a subform(continuous) on an unbound form. I also had a text box and a second subform(more controls but these are enough for the example). I had code in the subform (ON CURRENT and BEFORE UPDATE). I aslo had stuff on the subform(ON ENTER and ON EXIT). In each of these areas I placed a MSGBOX with the name of the area...so I could see in exactly what order everything fired. In the ONCURRENT I requeried the 2nd subform. To my amazement I learned that the BEFORE UPDATE was firing upto 3 times depending on how I was navigating. I finally figured out what I needed...thanks Everyone. It was definetely an education exercise. Mark A. Matte