Mike, it sounds like your FTP is just now failing and that using the ftps://... was working for you.

When using ftps we use curl and it, to the best of my knowledge, supports TLS 1.1 and 1.2.

The fact that filezilla is asking you about the certificate however is unusual.  TLS (like SSL before it) was designed to silently validate and accept certificates without user intervention.  I question why filezilla would ask you to accept their certificate, unless the certificate itself is invalid.

As we discussed at the last DIreXions, there are many reasons for a certificate to be invalid.  The most common one we run across is that the certificate has expired.  Basically when you get a certificate it comes with an expiry date and after that date the certificate will not be accepted.

Another possible issue is that the certificate cannot be or can no longer be trusted.  This recently has come to the forefront with both Chrome and Firefox canceling their trust of certificates issued by Symantec.
https://www.templarbit.com/blog/2018/09/07/the-story-of-why-chrome-and-firefox-will-soon-block-sites-with-certain-ssl-certificates/
https://blog.mozilla.org/security/2018/03/12/distrust-symantec-tls-certificates/

I would suggest you see if you can determine why filezilla is asking you to manually accept their certificate as, if it has expired or was from Symantec, it may explain why *web/ftp is no longer working for you and won't until the host replaces their certificate.

The variable REPLACEMENT_FOLDER$ should be set top the name of the panel which is to replace the current folder.

I have attached a sample export of a panel library that demonstrates what I am describing relative to using REPLACEMENT_FOLDER.  You should be able to import this into a library and then run the DEMO panel.

Why not control the Tabs yourself?

Basically create the container panel with a folder set as tabless.  Define one panel in it to be the default to be displayed.

Add a series of radio buttons across the top of this panel above the tabless folder. For each button set the text to be an expression such as TAB_1$, TAB_2$, .. and set the on press logic for the radio buttons to REPLACEMENT_FOLDER$=EVS("FLDR_"+STR(rb_value)+"$")

Now when the container panel is loaded have the pre-display logic load the values into TAB_1$/FLDR_1$ ... based on the userid and their desired tabs and tab order.  In the Post_display logic set REPLACEMENT_FOLDER$ to FLDR_1$ and hide any unused buttons.

You can add a extra button(s) to the right/left of the radio buttons should you want/need to provide the ability to scroll the list of folders.  Pressing on these buttons simply loads a different set of text and FLDR_nnn$ values.

With a little tweaking you should be able to come up with a fully dynamic folder style display that will allow you to specify your own list of folders and order by user.

Just to be sure you are running the correct ODBC Admin -- the shortcut runs:

%windir%\syswow64\odbcad32.exe

And the title bar of the Windows reads:

ODBC Data Source Administration (32-bit)

You probably should submit a help desk ticket regarding this issue, however folder tabs defined in your Nomads panels should work.  We have clients using this functionality none of whom who reported any problems. 

If you are manually adding tabs in your code or invoking the *obj/Folder object, then you may have issues.  Dynamically created folders are not supported within iNomads due to the nature of the panel->HTML conversion where folder regions and tabs need to be created up-front during the panel initialization process.

If however your folders are defined in the Nomads panel they should work fine.

There are a couple of methods you could use to do this.  Determining the easiest will depend on your applications.

Fundamentally you need to intercept the data just prior the file update (pre-WRITE) and make sure the fields are needed. 

Now if you are using the standard Nomads File Maintenance utilities you can create an interface program which can be PERFORMed before the write at the entry point FM_PRE_WRITE.  It it wants to cancel the write due to missing data it simply sets _IF_ERR$ to the message to display.

This seems to work for me.

I just tried dragging a Nomads panel to my secondary screen (to the right of the primary) and maximized it.  I then shut everything down and restarted.  The next time the panel was invoked it returned to the secondary screen maximized as expected.  I also tried this after switching the position of my secondary monitor to make it on the left of the primary (thus at negative pixel offsets).

I suspect it may be something in your winpnl.