Please Login or Register to view this content.
Please Login or Register to view this content.
Last edited by AliGW; 05-28-2022 at 04:20 AM. Reason: Code tags added.
Welcome to the forum.
Please don't just dump a whole load of code into a post and expect someone to be able to help you without a clear explanation of the issue.
Administrative Note:
You need to include code tags around your code.
Please take a moment to add the tags. Posting code between [code]Please [url=https://www.excelforum.com/login.php]Login or Register [/url] to view this content.[/code] tags makes your code much easier to read and copy for testing, and it also maintains VBA formatting.
Please see Forum Rule #2 about code tags and adjust accordingly. Click on Edit to open your post, then highlight your code and click the # icon at the top of your post window. More information about these and other tags can be found here
(Note: this change is not optional. As you are new here I have done it for you this time.)
Ali
Enthusiastic self-taught user of MS Excel who's always learning!
Don't forget to say "thank you" in your thread to anyone who has offered you help.
You can reward them by clicking on * Add Reputation below their user name on the left, if you wish.
Forum Rules (updated August 2023): please read them here.
I will agree with AliGW, we cannot help debug this without some detail about what "works" and "does not work" mean.
I will add, though, that a big part (half??) of programming is debugging. Are you familiar with VBA's debugging tools (quick tutorial here: http://www.cpearson.com/excel/DebuggingVBA.aspx?em_x=22 )? I find that one of the first things I will do with something like this (whether my own code or someone else's) is to put a Stop statement or breakpoint at the top of the function (and, as debugging goes on, elsewhere in the function procedure) so VBA can enter debug mode and I can debug the procedure. The basic idea of debugging is to execute the procedure one statement at a time and identify which statements are doing something unexpected. Then figure out why the logic of that statement is incorrect and come up with a new statement that is correct.
Hopefully that will help get you started debugging on your own.
Originally Posted by shg
I suggest uploading a sample file and explaining in step by step detail...ignoring your code...what it is you are wanting to achieve...Showing a before | after scenario...
99% of the time, a simplified solution can be offered...
Good Luck
I don't presume to know what I am doing, however, just like you, I too started somewhere...
One-day, One-problem at a time!!!
If you feel I have helped, please click on the star to left of post [Add Reputation]
Also....add a comment if you like!!!!
And remember...Mark Thread as Solved.
Excel Forum Rocks!!!
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks