Else warning not being triggered

[nigelog]

I wanted to add a safeguard to a database amendment command to ensure that the details were written back to an exact match in the search column

The code works

If I remove a few letters from the name in Ddtxt_01 the code will ignore as no match and no cells are overwritten

But the warning message isn't shown. What am I missing in the order of the code

Please Login or Register  to view this content.

[AB33]

There are a number of errors on your code, but all are masked by resume next.

Please Login or Register  to view this content.

[Arkadi]

With lrow as a range you would need "SET" in front of the Find, but with .row that will not work, unless I'm very mistaken. I might suggest a small change to AB33's code (try his in case I'm wrong, entirely possible):
I removed .Row from the find, other changes in red

Please Login or Register  to view this content.

[AB33]

Arkadi,
Yes, you are right. I did not test the code. I was trying to press home that the error trapping is hiding the error.
I used to put this hideous line at the top of my code in the hope that the code does not error and simply runs. Looking back, I cringe. .

[Arkadi]

@ AB33 IKR! I did it too, I must admit that sometimes for a single line or set of lines I implement on error resume next, but that is in a very controlled and limited context.
Skipping errors is not a great way to go 999 times out of 1000.
Btw, thanks for the rep AB33, not required but appreciated

@nigelog, when using "resume next", which is usually not the best solution, if you experience problems, disable it at least temporarily to troubleshoot, then once you are satisfied (or have gotten to the source of the problem) you can always re-enable it.

[AB33]

That is precisely how it should implement it. You need to remove it after you trapped the culprit line, but leaving it open makes all the subsequent errors to be hidden.
I think Microsoft should put in a big sticker warning when ever some one use this line to warn them its pitfalls. Novice programmers might not aware its deadly consequences.
Some people also misuse or even abuse it, like the try and catch in C driven languages.

[nigelog]

Thank you both for your educational comments.... had wondered how wide a scope On Error Resume Next command had

All sorted - many thanks - will mark as solved

[Arkadi]

Glad we could help nigelog