Button Control on Tab-Control Pages

[ijared]

1)I have navigation tabs on the first tab and it controls all the records on these tabs (pages).

I want the navigation tabs to work only in tabs 1 and 2 but a second navigation tab to work on tabs, 3 and 4. (It can be the same navigation tab and works the same way but when the first navigation tabe moves, the records in Tab (page 3 and 4 ) doesn't move.

If I go to Tab (or Page 3) the records in Tab (page 1 and 2) doesn't change.

[twinnyfo]

ijared:
If I go to Tab (or Page 3) the records in Tab (page 1 and 2) doesn't change.

Is this the way you want it or the way it is right now?

Either way, because you are talking about Records in the Tab Control, there is no way to do what you are wanting to do without changing the structure of your form and using Sub-Forms which are not linked in a Parent-Child relationship with the main Form.

We have said this before. It does not appear you are using Sub-Forms within your Tab Control Pages, but the data is simply in Text Boxes on those Pages.

It is impossible to move to part of one record on one page and another part of another record on another page without the use of Sub-Forms.

[ijared]

All my records in the dtabase are one one page. I am not trying to change anything in the records apart from deleting the record when it is not in need.

[twinnyfo]

Yes, if you delete the record on one Page, you will delete that same record from the other Pages as well. You must restructure your Tab Control and use Sub-Forms.

[ijared]

I want things to work just as you say. When I delete or edit something, I want it to affect everything.

[twinnyfo]

That is not how your original post reads.

Exactly what is it that you are trying to do.

Please--do not simply restate the same things you have said many times before, as apparently we are not quite grasping it.

This is what I hear: You want to navigate to different records on Pages 1 and 2 of your Tab Control using Navigation Command Buttons that you have put on your Tab Control on Page 1. You want a different set of Navigation Command Buttons on Page 3 (or 4) of your Tab Control that navigate the records only on Pages 3 and 4. We have grasped all that. However, you can't have it both ways. You can't delete a record that is being displayed on all four Pages, yet still navigate to different records at the same time.

Please help clarify this for us, as we are thoroughly confused.

[ijared]

ok. thanks. I will rethink about it.

[ijared]

What about if I use the same command button? Will it be the same result?

[twinnyfo]

Moving to a different record is moving to a different record. You can have twelve Command Buttons, but if they change the record, the entire record of the Form will change--unless you completely restructure your Form.

[zmbd]

ijared:
It appears that you do not understand the tab-control

Basic usage of the tab control, bound to a recordset, is to allow you to group information from a single record in a logical way and display that record's information in a format that allows the user to quickly find that information without scrolling or having a form design that "hurts the eyes" due to clutter

By way of simple example:
For an Employee record
On the main form you might display the Employee name and Badge number
On the TabControl
- Page1 may have the Hire date, Department, Supervisor, Work Email, Telephone-Extension, and picture of the employee
- Page2 may have the Home address, Home Telephone, Mobile number, Birthday
- Page3 may have information about spouse, kids, etc...

Now if you use ANY method of record navigation, doesn't matter if it's a custom command button or the default form record navigation (see here) ALL of the information will change on the main form and ALL of the TabControl Pages.
There is simply, absolutely, no way around this behavior on a bound form - period, dead stop.

IF you have an unbound form with an unbound TabControl then we have a new situation wherein you can setup subforms which could allow you to navigate records between forms independently; however, I do not recommend this method for people that are not extremely proficient in Access (or for that fact any database) and it doesn't sound to me as this is what you are doing.


>> What I'm getting from you now is that
You want record navigation controls on Tab-Pages 1 and 2
AND
on Tab-Pages 3 and 4 you want command buttons that will step thru the listboxes on those pages.

Finally,
Command buttons are NOT TABS
You simply MUST start using the standard names for the controls on the forms or no-one is going to be able to help you and not doing so after several requests show a certain lack of respect on your part towards those that are attempting to help.

[Rabbit]

I reset my answer because clearly it isn't the answer.

I'm just as confused as everyone else, I have no idea what is going on or what it is you want to do.

You should attach screenshots of what you have and mockups of what you want to do.

[ijared]

Any help please. I am adding a subform to my database but I need help as to what I should remove from my original database and put in there that will help my problem of navigation controls on Tab-Pages 1 and 2 etc, and command buttons that will step thru the listboxes on Tab-Pages 1 and 3.

[twinnyfo]

I still think you are going to have to give us more information on this one. Why would you need Command Buttons to step through list boxes? And, how is this tab control and its pages going to be related to your main form.

The more information you can give us the better. We have spent more than 40 posts trying to figure out that you couldn’t do what it was that you originally wanted to do and now we have to figure out a more complex solution—again, without much information on anything.

Please provide as much detail about your form and exactly what it is that you want to do.

[ijared]

Hi,
This is what I want to do:
1:Listbox to be able to select volunteers or use command buttons to browse through voluntees.
2.Personal details.
3.Comments
4.No longer volumnteers Yes/No
If No longer volumnteer admin can remove the person to no longer volunteers page when this person decides he/she doesn't want to do this anymore..
5: Why they decide to quit, admins can be able to delete volunteers.
------------------------------------------------------
1. Just like first 2 pages.
2.listbox like in third page like on first page.
3.comments
4.No longer volumnteers Yes/No does not show here.

Members not authorised to edit and change details shouldn't.
I hope this helps.

[zmbd]

This is what I want to do:
1:Listbox to be able to select volunteers or use command buttons to browse through voluntees. (...)

Ok, this is a standard membership type database - that makes sense.
A tab-control makes a lot of sense here in that by using the standard form-record-navigation controls you can display information in logical groupings.

HOWEVER,
What I gather you want to do with a standard bound form and a standard tab-control simply isn't reasonably possible.

Instead what I would do is create three forms
(I'm going to use a naming convention here that helps me to keep things straight):
Form 1 name it 100_Membership_ Navigation

- this is unbound

Form 2 name it 110_Membership_ List

- SUBFORM TO 100 - this will be a continuous form bound to a record-set that lists the basic member's identification such as ID number, name, and most likely a field that indicates volunteer status

Form 3 name it 120_Member_Prof ile

- SUBFORM TO 100 - This form will be bound to a record set with the members details. This will be a "Single" form view using a standard tab-control. Looking at your post#11 it's very difficult to tell how to group the data; however, logical would be Page1 would have availability, special skills, and other information to help match with task at hand, Page 2 would have personal contact information

So on 100_Membership_ Navigation I would place a TextBox that will be bound to the 110_Membership_ List record's primary key - this way its value changes when the current record changes on 110_Membership_ List. This control will be hidden. This control will be used to setup the Parent/Child relationship between 110_Membership_ List and 120_Member_Prof ile

I've ran out of time for right now; however, this afternoon/evening (CST) I'll upload a simple example database showing how this can all be setup.


------------------------------------------------------

1. Just like first 2 pages.
2.listbox like in third page like on first page.
3.comments
4.No longer volumnteers Yes/No does not show here.

This is really just a re-hash of the previous explanation and really doesn't help.

Members not authorised to edit and change details shouldn't.

As for Administrator verses Non-Administrator privileges to delete a member from the database... that's a whole other topic in and of itself and covered many times in other threads.