The current implementation of the Top10 auto-filters in Excel is horrible.

There are four 'Top 10' filters: xlTop10Items, xlTop10Percent, xlBottom10Items, xlBottom10Percent

Problem 1) The names are deceiving. They are not always 10 items or 10 percent. Better names would be Top X Items or Top N Items.

Problem 2) The Excel object model does not allow the original criteria to be retrieved. If you create a Top 10 Items filter with the value 15, then the Filter.Criteria1 property will be changed to a >= criteria depending on the data in the column and the original value of 15 has no way of being retrieved via the Excel object model. This is a major problem for macros which want to copy filter settings from one table to another.
see 'Discovery #4: Top 10 Settings Are Weird': http://yoursumbuddy.com/autofilter-v...or-parameters/

Problem 3) The xlTop10Percent and xlBottom10Percent filters allow integer values between 1 and 500. What is 500% of a data set? It makes no sense. Perhaps decimal values between 0 and 100 would make the most sense, but at least update it to integer values between 1 and 100.

Hello.
Over the years, I've found that I needed a filter, which I could modify, using VBA, that would allow me to filter more than a single component when I'd activate it. Last year, I posted on the MSDN-Excel for Developers forum, and one member gave me a sample which I modified, and got to work for my purposes.

https://social.msdn.microsoft.com/Forums/en-US/2e738c1e-ca46-4511-8d93-4ba870468aea/multifilter?forum=exceldev

I took his sample, made the changes, and now have an excellent filter tool (I posted my final solution, and have made several using different numbers of components), and thanks to VBA, I can add, remove, increase, reduce, etc... my filtering capabilities, as needed.

The other day I found that the basic autofilter would not allow me to filter based on the does not contain or does not equal options in the way I wanted/needed. I thought about it, and recorded a macro, using the filter, and the "does not contain" option. I then took that, applied it to my filter macro, and found it did not work. I posted back on the forum, discussing my problem, and learned that the Autofilter tool and the options I used are incompatible, and do not work together.
As such, I'd like to ask for some work on your guys' end to change this option to allow us to gave full usability for autofiltering with VBA.

https://social.msdn.microsoft.com/Forums/en-US/77a87942-eddb-4efd-ac98-448b659f174a/custom-filter?forum=exceldev

is my most recent foray, and attempt to use the "does not contain" option for the autofilter. Eg.

Criteria1:="<>*" & arr & "*"

where I could expand the criteria to include more than a single element. Presently, my existing code shows the Criteria1:= arr
Why could I not also add standard coding elements to expand its operability?
As you know, the "<>*....*" would be the recorded results for the "does not contain" option. It seems an easily accomplished transition to code a variable where the '....' would be, giving what I have above in my sample.

In all honesty, while I'm told I keep pushing the envelope with the ideas I come up with, I know I cannot be the first one to think about this. Please review, and act on this.... my filtering needs are clamoring for it to work, and the other solution is too limiting.
TYIA.

The Format (or VBA.Format) function is part of the VBA language, not the Excel object model. This means that this function is not available to .NET COM addins (VSTO, AddinExpress, Excel DNA). This can be a problem for the development of new addins using .NET or upgrading existing VBA addins to COM.

Note that .NET has string.Format() and Microsoft.VisualBasic.Strings.Format() but neither of those has the same behavior as the VBA Format function especially with regards to dates.

Note that there is a similar function that is part of the Excel object model: WorksheetFunction.Text(). However, this function still differs from the VBA Format() function. It would be nice if the Format function could also be included in the excel object model as WorksheetFunction.Format() so that it can be accessed from .NET addins

I've made a code for studying function SIN and COS. It's like an analog clock that shows only second hand(Line shape).
It works as expected with Excel 2013. But with Excel 2016, second hand(colored red) cannot be seen, only marks(both ends of Line) can be seen.
I've reproduced this, in Windows 7, 8.1, and 10.
--- my code ---
' --- for "Sleep" スリープ関数(API)の宣言
Declare Sub Sleep Lib "kernel32" (ByVal dwMilliseconds As Long)

' ---[10] Analog Clock (display second hand) （アナログ時計・秒針を表示：サイン、コサインの練習）
Public Sub prc_Show_AnalogClock()
Call prc_Clear_Clock ' -- delete Oval and Line already exist: 既存の円と直線を削除
Application.ScreenUpdating = True
' --- decide location of Cell C13: 位置の決定（セル C13 の座標：左上）
Dim posX As Single, posY As Single
posX = Range("C13").Left
posY = Range("C13").Top
' --- get diameter of Oval: 円の直径を入力
Dim inputString As String
Dim myDiameter As Single ' -- diameter of Oval: 円の直径
'inputString = InputBox("円の直径(pixel)を入力して下さい。", "円の直径")
inputString = InputBox("input diameter of circle", "diameter")
If inputString = "" Then
Exit Sub
Else
myDiameter = CSng(inputString)
End If
' --- add shape Oval: 円（楕円：縦=横）を描く
ActiveSheet.Shapes.AddShape(msoShapeOval, posX, posY, myDiameter, myDiameter).Select
' --- setting of Oval: 塗りつぶしの設定
With Selection.ShapeRange
.Fill.Visible = msoFalse ' -- 塗りつぶし無し
.Line.ForeColor.RGB = RGB(0, 0, 255) ' -- 線の色
.Line.Weight = 1.5 ' -- 線の太さ
End With
' --- starting point of second hand: 秒針の始点
Dim startX As Single, startY As Single
Dim endX As Single, endY As Single
startX = posX + (myDiameter / 2)
startY = posY + (myDiameter / 2)
' --- ending point of second hand: 秒針の終点（１秒ごとに変わる）
Dim DurationSec As Integer ' -- how long display short hand: 持続時間（秒）
Dim iSec As Integer
'inputString = InputBox("表示時間（秒）を入力して下さい。", "表示時間（秒）")
inputString = InputBox("input duration time(second)", "duration time")
If (inputString = "") Then
Exit Sub
Else
DurationSec = CInt(inputString)
End If
' --- add/delete shape Line at interval of 1 sec: １秒間隔で線（秒針）を描く（サイン、コサインの練習用）
Dim mySec As Integer
Dim myConst As Single
myConst = 3.141592 / 180
For mySec = 0 To DurationSec
endX = Sin(6 * mySec * myConst) * (myDiameter / 2)
endY = Cos(6 * mySec * myConst) * (myDiameter / 2)
' --- add Line: 秒針を描く
ActiveSheet.Shapes.AddLine(startX, startY, startX + endX, startY - endY).Select
With Selection.ShapeRange
.Line.ForeColor.RGB = RGB(255, 0, 0) ' -- color of Line: 線の色
.Line.Weight = 1 ' -- weight of Line: 線の太さ
End With
DoEvents
Application.ScreenUpdating = True
' --- delete Line after 1 second: １秒待ってから、秒針を消す
Sleep 1000 ' --● Sleep API declared on the top: モジュールの先頭でスリープ関数(API)を宣言している
If (mySec < DurationSec) Then
Selection.ShapeRange.Delete
End If
Next
' ---
MsgBox "Clock stopped: 時計終了"
End Sub
' --- delete Oval and Line already exist: 既存の円と直線を削除
Private Sub prc_Clear_Clock()
Dim myShape As Shape
For Each myShape In ActiveSheet.Shapes
'If (myShape.Type <> 12) And (myShape.Type <> 6) Then
' MsgBox "Shape Type=" & myShape.Type & Chr(13) & "Shape Name=" & myShape.Name
'End If
If (myShape.Type = 1) Or (myShape.Type = 9) Then
myShape.Delete
End If
Next
End Sub

It seems clear from https://excel.uservoice.com/forums/304921-excel-for-windows-desktop-application/suggestions/8843113-bring-vba-into-the-modern-world that while VBA will stay for a while, the future is to replace it with JavaScript. Cross-platform, modern, I don't entirely like it but I get it.

So today I sat down to start learning JavaScript and consider building anything I would have put in VBA in it instead, and so far it appears I'd need to do so in Visual Studio or a text editor. Is this correct? That same link notes that you'll create "a more modern editor than the VBE" but only after broadening the API set (at which point you'll look into recording too).

Can I suggest reordering these priorities? It is a major advantage in VBA to have the editor as part of the program. It means I can create VBA code in an Excel sheet and then if a user has a problem I can debug it right there on their machine. Or if I'm teaching someone new to coding the step of setting up and explaining a separate editor and the debugging process and getting them running is MUCH faster, easier, and simpler; it is such a huge advantage when the IDE is already on their machine.

If you're genuinely looking to eventually make JavaScript the norm I think you should do this now to help people start up the learning curve faster. Then we'll all be with you as you build out the API set rather than only starting on our learning curves when you're done. Or, if such a thing already exists, please make it clearer as a fair bit of time searching for starting tutorials and/or explanation of the new JavaScript API haven't netted me anything truly useful yet.