[AccessD] Setting .AllowEdits programmatically

John - I used to try to use the current event, but eventually gave up.  It
fires under many circumstances - trying to anticipate or control them all is
quite the exercise.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Saturday, August 06, 2011 11:12 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Setting .AllowEdits programmatically

Causes the current event to fire.

I was running code

	.AllowEdits = mblnFrmEditMode

and the current would fire immediately.  I ended up having to wrap the code
in the following to *minimize" the current event firing even when it was
already the same state.

         If .AllowEdits <> mblnFrmEditMode Then
             .AllowEdits = mblnFrmEditMode
         End If

No idea why this happens but it does.  I also have no idea whether setting
the .AllowDelete and .AllowAdd causes a current event to fire.

--
John W. Colby
www.ColbyConsulting.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com