We have no access to your data, or any idea what that code is supposed to do - let alone what it is doing that it shouldn't.
If you are following an online tutorial, the best place to start is with the tutorial itself: ask about your problem there, and at least they know what the background is and should be able to help you, where we can't.
If they don't or can't ... find a different tutorial - the author of one you are following probably knows very little more than you do!
Quote:
Quando eu executo o código, dá o erro:
Sub, Função ou Propriedade não definida.
não sei se srá de você meu excell estar em português e a semântica é diferente,
worksheet= Folha
ThisWorkSheet = EsteLivro etc, como disse estou a me inciar em vba.
Muito obrigado
"When I run the code, it gives the error:
Sub, Function or Property not defined."
That means exactly what it says: you are trying to use a subroutine, function, or property that you haven't declared, or that you have misspelled.
If you look at the error message, it will tell you which line of your code it found the problem on, and that should tell you what you need to look for.
This may help: You should expect to get syntax errors every day, probably many times a day while you are coding - we all do regardless of how much experience we have! Sometimes, we misspell a variable, or a keyword; sometimes we forget to close a string or a code block. Sometimes the cat walks over your keyboard and types something really weird. Sometimes we just forget how many parameters a method call needs.
We all make mistakes.
And because we all do it, we all have to fix syntax errors - and it's a lot quicker to learn how and fix them yourself than to wait for someone else to fix them for you! So invest a little time in learning how to read error messages, and how to interpret your code as written in the light of what the compiler is telling you is wrong - it really is trying to be helpful!
So read this:
How to Write Code to Solve a Problem, A Beginner's Guide Part 2: Syntax Errors[
^] - it should help you next time you get a compilation error!
And spending a little time learning to understand syntax error messages will save you a huge amount of time in future: you waited at least 1/4 hour for Chris to reply, then your email system probably added another 10 minutes or so, plus the time it took you to type up the question once you had found this site and created an account. Chances are that you could have saved a significant chunk of that time if you knew how to read them!
I'm not saying we don't want to help you fix them - sometimes I can't see my own errors because I read what I meant to write - but fixing syntax errors is part of the job, and if you can't do it for yourself people are going to look at you as a bit weird should you get a job in the industry!