As the others have said, that many textboxes on a single form is a pretty poor UI design: it's difficult to manage, difficult to code for, and difficult for a user to process.
It also probably looks very ugly! :D
If you need to present or request significant data to / from a user, then a better approach is to either use TabPages to break it up into groups of related items (as Visual Studio does with the "Project Properties" options when you double click on the "Properties" branch in the Solution Explorer) or to use a table based control like a DataGridView if the data is row / column based.
By throwing textboxes at the problem you are making a rod for your own back!
But ... having said that, you don't generally have to code a TextChanged event for each textbox - the same handler code can be associated with multiple controls as each time it is called it is passed two parameters: the
EventArgs e
and the
object sender
. The first describes the event and provides addition info about it in many cases; the latter is the Control instance that raised the event and you can cast that to a TextBox:
Private Sub myComboBox_TextChanged(ByVal sender As Object, ByVal e As EventArgs)
Dim tb As TextBox = TryCast(sender, TextBox)
If tb IsNot Nothing Then
Console.WriteLine($"Text Changed: {tb.Text}")
End If
End Sub