Forcing Refresh/Data Changes Saved in Mutli-Tabbed Form

[JoeM]

I have a multi-tabbed Data Entry Form in one of my databases.
Is there a way to commit/save all data changes on the event of switching from one tab to another?


I have some tabs that are dependent on certain check boxes being selected on other tabs, and if users select the check box, it doesn't enable the fields on the other tabs right away (unless they switch records which then triggers the update to be written, and then come back into it).

I could use the After Update Event on each particular check box field, but would prefer if there was just a way to "force" save/commit all changes upon the movement from one tab to another.

Thanks

[June7]

I just tried the Click event of tab control as well as the tab page and nothing happens. Weird. Why is it there if it does nothing?

Just saving the record will not enable the other fields unless you are using Conditional Formatting.

[JoeM]

Just saving the record will not enable the other fields unless you are using Conditional Formatting.

It isn't that kind of enable sort of thing. It is more creating the records that link to the other tables sort of thing.
I'll just try putting a "Me.Refresh" line in the After Update event of that one field. I was hoping I could do that on the switching of a tab, but it does not look like that is an option.

Thanks

[ItsMe]

Refresh will not requery the form's recordset/tables. Using Me.Requery will bring the user to the forms first record. Maybe an acSave command or something.

You can reference tabs in a Tab Control by using the control's tab indexes. Me.TabControl.Value = 2. So you could requery specific controls using the tab control's click event handler. In the click event you could place a Select Case statement.

Case tab.value = 2 Me.cboCust.Requery

[JoeM]

Interestingly, when I just tried the Me.Refresh, before I used it, it would show the "pencil" icon, indicating that the Access record hadn't been saved or committed yet.
But after I added the Me.Refresh, that icon went away, indicating that the record had been saved. So I think that *seems* to do what I want...

[ItsMe]

The way I understand it..... Exiting a bound control will change the value in the table. Saving a record will eliminate the form's memory of the changes you made. Ctrl + Z or Undo will not be effective after you save a record or navigate to a new record within a recordset.

[RuralGuy]

As you have discovered, the "Click" event of a Tab Control is pretty much useless. That is why we use the Change Event of the Tab Control instead which does fire every time you change tabs.

[ItsMe]

As you have discovered, the "Click" event of a Tab Control is pretty much useless......

My experience with the click event handler for tab controls has always been positive. Clicking any tab on the control fires the code in this example that uses the click event handler.

[JoeM]

That is why we use the Change Event of the Tab Control instead which does fire every time you change tabs.

I think that is precisely what I was looking for! I was looking in the wrong place (at each individual tab instead of the Tab control).
Thanks!

[June7]

ItsMe - I tried your sample db, nothing happens with Access 2007. The Click event is non-functional, however Change does the trick. Thank you M$!

[Missinglinq]

...Clicking any tab on the control fires the code in this example that uses the click event handler...

That's odd! Your example doesn't work when I download and run it, and, as Allan suggested, this kind of code never has!

Linq ;0)>

[ItsMe]

Yup, I must be getting too comfortable with A2010. I did a quick study with a new control in A2003 and discovered the click event kinda functions. The problem is, it only functions outside of the page and outside of the tabs! You have to click in the header, so to speak.

[ItsMe]

That's odd! Your example doesn't work when I download and run it, and, as Allan suggested, this kind of code never has!

Linq ;0)>

I just tested that DB again in A2010. It does work when the tab is clicked. I did not consider different versions until June mentioned 2007. Crazy stuff. Maybe they switched it back for 2013.