Charlotte Foust
cfoust at infostatsystems.com
Mon Sep 21 17:21:29 CDT 2009
Excuse me? It's easy enough to determine which tab was clicked, just raise an event, for one way. Why need a gazillion event stubs for all those buttons when you can handle it all in one routine? Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo Sent: Monday, September 21, 2009 3:16 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Update or CancelUpdate Without Addnew or Edit ..and then you have to jump through loops to see which tab control was clicked. And you cannot change its colour, etc. you are stuck. Use a button or a label simulating a tab/button and the world is your oyster (assuming you like fish - but then we are back to your other problem LOL). Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: 21 September 2009 23:09 To: Access Developers discussion and problem solving Subject: Re: [AccessD] Update or CancelUpdate Without Addnew or Edit > but why make extra work for yourself showing and hiding stuff with "buttons" on a single parent form and generally reinventing the wheel? Agreed. That is precisely what the tab control is for. Write the code and place it in a framework library... ;) John W. Colby www.ColbyConsulting.com