jwcolby
jwcolby at colbyconsulting.com
Fri Sep 10 09:04:52 CDT 2010
And all because AllowEdits implementation sucks! But hey, let's not worry about such things, and build pretty toolbars for future editions of Access. ;) John W. Colby www.ColbyConsulting.com On 9/10/2010 9:46 AM, Jim Dettman wrote: > > <<Now that is a solution to think about!>> > > Probably not; snapshots are a major performance hit. With a snapshot, your > asking JET to make a complete copy locally of everything that is in the > recordset. If your pulling that over the wire, that will take some time. > > Only place this would work well is if the recordsets were very small > (dozen or so records at best). > > Jim. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Friday, September 10, 2010 8:59 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] can't select data in control when AllowEdit false > > Asger, > > Now that is a solution to think about! > > I will have to take a look at whether my code can do that to the form as the > form opens. My PLSS > reads information about what groups are allowed to perform the various > activities in a form. While > it seems unlikely to occur in real life, the objective is to easily and > intuitively allow specific > groups to have the authority to add, delete and edit records. > > In theory a group could be allowed to delete or add, but not allowed to > edit. A snapshot would > prevent the edit but would also prevent the add or delete (I think). > > John W. Colby > www.ColbyConsulting.com