Not that I know of at this time, but you would know this number at design time..
If you want to limit the changes you would have to make in code, then use a variable at startup that has the page count and then reference that variable in your code. Then if you add or remove pages you only have to change the PageCount variable. ----- Original Message ----- From: "Charles Parks" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, December 20, 2004 10:53 AM Subject: [RBG7-L] - Re: Looking for a way Is there a property command that counts how many pages there are within a tabcontrol so that I could enable/disable the previous/next buttons based on what the activepageindex is? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of A. Razzak Memon Posted At: Saturday, December 18, 2004 3:56 PM Posted To: RB7-L Conversation: [RBG7-L] - Re: Looking for a way Subject: [RBG7-L] - Re: Looking for a way At 04:41 PM 12/18/2004 -0500, Mike Byerley wrote: >Instead of panels, I just set the TabVisible property to false and use >buttoons to navigate between pages on the tab control. Exactly! And here is how: Hide all un-necessary pages (such as page 3) until you do the checks. If all is well then show that page on demand. By default you'll need to hide those pages. You'll do that in "On After Start EEP": PROPERTY <EnhancedTabPage3ComponentID> TABVISIBLE 'FALSE' This will hide that page, by default. Then, in your Exit EEP where you're doing all checking: IF vCheckVar = 'GoodValue' THEN PROPERTY <EnhancedTabPage3ComponentID> TABVISIBLE 'TRUE' PROPERTY <EnhancedTabPage3ComponentID> ACTIVEPAGEINDEX 2 ELSE PAUSE 2 USING 'Missing Data or whatever ...!' ICON STOP ENDIF RETURN Very Best R:egards, Razzak.
