Fred 

Maybe I tricked myself regarding the opeTable command.  I actually have 2 commands in the button script (sorry for the confusion in my original post):

openTable("Supplier", "Inventory");

openRecord(first(select Supplier),"Inventory")

I can confirm that in Mac app 3.14.3 the above script will leave the LaunchPad table and switch to the Supplier table and display the 3rd tab in the Supplier table. -- this is the desired behavior.

However, if the script is simply:

openTable("Supplier", "Inventory")

In Mac app 3.14.3 the script will leave the LaunchPad table and switch to the Supplier table but display the first tab - ignoring the tab parameter "Inventory"

When I was messing the the database on the clients public cloud 3.15 I could copy and paste a "fresh" version of the first script above and the behavior would "work" the first time, i.e, Leave LaunchPad table and land in Supplier table tab 3 (Inventory) but, subsequent "button clicks" would yield the behavior of leaving the LaunchPad table and landing in Supplier table tab 1.

Scripts that switch between tabs of the same table work using the openRecord command.

I guess the openTable command never really "worked" in that it simply switches to the named table and lands on the first view, whatever it is, and ignores the named view parameter.

Apparently, since I paired it with the openRecord command I got the result I wanted.

So, again in Mac app 3.14.3

By itself, openTable("Supplier", "Inventory") only switches from the LaunchPad table to the Supplier table but ignores the tab parameter and instead lands on tab 1

By itself, openRecord(first(select Supplier),"Inventory") switches from the LaunchPad table to the Supplier table and lands on the Inventory tab (tab 3)

Fred 

Hi Fred -

The LaunchPad where the button is located is a form view.  The LaunchPad associated table just has one record.

The Supplier table has many records and has one form view with 3 tabs.  The button used to land on the form view tab 3 (Inventory) now it lands on tab 1.

As mentioned, I can get the public cloud 3.15 version button to work once after "refreshing" the script.

Uploading the DB would be problematic since there are lots of references in field names and the like that are proprietary.

I might be convinced to DM to you at the great risk of you laughing me for what is likely crummy programming compared to the likes of your gteat expertise!

Fred 

Thanks!  Tried out your DB and it performed as I think you expected.

I attached your DB with a slight change.  I added a Tab to TableA Form.  The first Tab in Form I guess defaults to TableA.  I added a Tab called "Extra Tab" just before the Yes/No field in the Form field list.  I then added "Extra Tab" to the Select View choice field.  Then when I click button 'Open Table and View' I get the behavior I am seeing.

It switches to TableA and lands on TableA tab and not on Extra Tab.

Sure appreciate you playing along with me!!

Mel Charles 

Not sure what you mean re using openRecord as a workaround.

openRecord does not open 'secondary tabs' in the public cloud after 3.14

openRecord did open secondary tabs in the Mac app but, now that the Mac app has updated to 3.15.2 it does not open secondary tabs.

Everyone has an opinion... mine is that popupRecord & openRecord are key to UI particularly if your Ninox solution is targeted at users vs developers.

Mel Charles 

Ah, yes I see our disconnect.

In the public could 3.15.2 openRecord() will not work for me when trying to go to a specific tab in another table.  Since you are using 'this' you are accessing a tab in the same table.  That works for me too.

However, if I use something like, openRecord(first(select TableA), "Extra Tab") it moves to TableA but lands on the first tab in that table and not "Extra Tab" which isn't the first tab.  So, again openRecord behaves if moving within a table but fails when moving to another table.  Thanks for your feedback!  Here's hoping Ninox fixes us up!