Charlotte Foust
charlotte.foust at gmail.com
Sun Dec 4 18:45:52 CST 2011
It makes sense to me. A control is either going to be multiselect or not. Why would you even want to change it on the fly? Charlotte Foust On Sun, Dec 4, 2011 at 4:15 PM, Darryl Collins < darryl at whittleconsulting.com.au> wrote: > Hmmmm... Turns out you can only set this property when the form is in > design mode, even via VBA. Why on earth would they do that? > > I have a couple of workarounds in the bag, so not looking for a solution > (unless you have a really cool one you can share), but it seems like an odd > thing to enforce on developers, especially as the form is nearly always > going to be open and in use when you want to change that property 'on the > fly'... > > Anyone got any thoughts on this? Just curious. > > Cheers > Darryl. > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > > > Website: http://www.databaseadvisors.com > > >