VBA Insert row causes Excel to crash

[BuddhaJoe]

Excel crashes (no response) when a value used in VBA is selected from a ComboBox. It does NOT crash when the value is entered into the ComboBox (rather than selected). My previous thread gets into all the attempted fixes that proved more of a distraction than anything. The Workbook has been totally rebuilt from scratch, so no chance of corruption.
Again, it works perfectly when the value is entered, but always crashes (method will vary) when the value is selected.

The VBA code inserts a row into the spreadsheet above the active cell, and then pastes the value from the ComboBox (actually from the cell linked to the ComboBox) in the LinkedCell Property.
The ComboBox also uses a ListFillRange called My_Range, which is a dynamic range based on a worksheet formula.

I have screenshots of the worksheet showing the 2 methods of entering the value mentioned above. Not sure how to attach them, as I have not uploaded them to get a URL.

I am grateful for the responses to my last thread, and look forward to ideas on how to proceed.

 

[BuddhaJoe]

Re: VBA Insert row causes Excel to crash: PART 2 (Declared victory too early)

Here are screenshots showing the 2 conditions:

https://imgur.com/a/sfUef

<tbody>
</tbody>

 

[BuddhaJoe]

Re: VBA Insert row causes Excel to crash: PART 2 (Declared victory too early)

LAST bit of even more detailed (and curious) information: As weird as this seems, entering (pasting) a "real" plant name from "the list" (in another sheet of the Workbook), causes Excel to crash, even though the plant name was NOT SELECTED from the ComboBox. SO . . . the key distinction seems to be whether or not the Plant Name entered results in a valid RANGE (the Defined Name "My_Range" referenced by the ComboBox Property ListFillRange.
WHAT THIS MEANS is: When a not-existent plant name is entered, the range formula evaluates to NOTHING. When an actual plant name is used (even if ENTERED rather than Selected), the Rangle resolves as valid Range. That's when VBA crashes Excel . . . Hmmmm