For the attention Of F Dibbins regarding not being able to connect

I have [pushed this to the TT, although, I dont see how you could have posed this if you cannot connect?

Hi jolivanes
See if this link is of any benefit for your issue...
https://www.excelforum.com/developme...-blockage.html

Originally Posted by jolivanes

..why it would throw the message. I tried without "Select" as mentioned in the site that John suggested .. no avail..... nice to know for the possibility of future posts...

Hi jolivanes,
Sorry I am a bit late on this: I caught this Thread of yours but then could not get near a computer for a while….
I think I know most of these things that throw the typical _...

Access Denied - Sucuri Website Firewall

-… thingy

The short answer to your question is … Yes, I know what is throwing the message in your case: This is what it is: In your code you do have the potential problems of two occurrences of the _ Select _ and also one occurrence of the _ Exec _…… _ ,
( _ Exec _…… _ is another thing known to throw the message *** in some cases _…… )
But, In your particular case , only the _ Exec _…… _ is giving you a problem.
You and Kyle have probably been distracted from that _ Exec _…… _ by looking only at the _ Select _ , which in this case is not giving you a problem _..
_... ( Indeed, you are using fairly typical / very common VBA uses of the word using the _ Select _ , and if those threw the message then we would have the problem a hundred times a day! , lol )

Here the detailed answer with explanation of the problem and workarounds to get anything you want posted
As you have probably gathered there is a software ( from a company Sucuri ) which is a Security Firewall protection thingy in place at excelforum that tries to catch attempts from spammers and the like at some sort of SQL ejaculating into the Forum…
At the “site” John gave you , ( that is a recent excelforum Thread ) , there are URL list of some of the many Threads in the excelforum
Suggestions for Improvement Sub Forum and other Off Topic Sub Forums ( where people often report these things.. https://www.excelforum.com/developme...ml#post4778069 )

You have got a couple of those sort of forbidden things in your code, which can potentially cause the Security Firewall protection thingy issues that you have experienced. One of these problems you have twice in your code. The other you have just the once in your code:
That is to say, there are two of the possible
_…Select…. _______ Problems, __ ( - specifically: .AllowMultiSelect and .Select )
and one of the
_…. Exec(“…. __ eXec ___…. __ _ Problems ( - specifically: Exec(" CMD )
(At the “site” John gave you there is also one of the Threads on the ….…..Exec(“…. __ exec …. ___ *** http://www.excelforum.com/the-water-...ml#post4502342 )


_….. You often get confused in particular with those two problems, as those two things that throw the message are the most unpredictable in their effect on the Sucuri Website Firewall,… that is to say , whether or not they throw the typical __ Access Denied - Sucuri Website Firewall __ message , depends on a number of factors related to what else is used in combination with them. ( I guess the Sucuri Website Firewall is set to catch possible coding ejaculations .. )

In those referenced Threads in that URL list you will find the different problems and the possible workarounds discussed.
You will find that you do not in fact have a problem with your Selects. Hence your attempt at altering those selects would have had no effect, as you found. You only have a problem with your Exec("
For a workaround in a case like yours , I personally usually tend to favour the “black character trick”. Using the “black character trick” allows you to see in, ( and copy from ), the final post exactly what you wanted to post with no seen alterations.
So for your case I would tend to do the following: When you are in the Forum editor with all there as you want it, then proceed as follows: Do the following

Highlight one or more of the characters in Exec(“
Then use the Forum editor character color selection icon to bring up the color selection and select the color black. So, for example you might then end up seeing in the Forum editor just before you post , in place of the problem giving character string in the code line containing that problem string , the following:

For Each file In Filter(Split(CreateObject("WScript.Shell").Ex[COLOR="#000000"]ec[/COLOR]("CMD /C DIR """ & startFolder & "*.xl*"" /S /B /A:-D").StdOut.ReadAll, vbCrLf), ".")

If you post that you will get in the finally posted Post exactly what you wanted to post :

For Each file In Filter(Split(CreateObject("WScript.Shell").Exec("CMD /C DIR """ & startFolder & "*.xl*"" /S /B /A:-D").StdOut.ReadAll, vbCrLf), ".")
( and by the way, you will get it with or without code tags: Sucuri is only concerned with the actual text you are posting: it makes no distinction between stuff as plain text or in code tags: Code tags have no effect on any of the typical things that throw the typical __ Access Denied - Sucuri Website Firewall __ message ) )

If you try to post that without that “black character trick”, that is to say you remove the code tag pair [COLOR="#000000"] and [/COLOR] then you will throw the typical __ Access Denied - Sucuri Website Firewall __ message.

You are actually addressing ( ### ) the
Exec("
Something like this is the important thing to do, that is to say this is what you see in the forum editor window: It is what you should post to get over ( fool ) the Sucuri Firewall:
E[COLOR="#000000"]xec[/COLOR]("

You can of course add code tags manually, by typing the code tag pair yourself rather than using the forum editor color icon. You can also alternatively use and type the worded BB Code color code tags ( http://services.runescape.com/m=foru...9,877,64690220 ) , which I prefer, so typing something like this will get over the problem also:
Exe[COLOR=black]c[/COLOR](“


You might be wondering why Kyle’s code seemed to post OK. That I think is explained as follows:

Firstly, it appears to me that currently ( Note, It may have changed slightly since I last looked at this problem ### ) the actual problem is caused by this character combination:
Exec(
If you brake that character chain up, for example as shown with the “black character trick” , then you fool Sucuri and you will get posted that without a problem.
Now, Kyle uses his tool a lot ( https://www.excelforum.com/the-water...extension.html https://www.excelforum.com/the-water...extension.html ).
He likes to use his tool a lot, because of the color that comes out when he uses his tool while posting code.
Now examine what he actually is posting ( you can see that , for example, by hitting the Reply With Quote Button, - then examine the code which is presented including all the BB Code tags )
You will see that around that problem character string his use of his tool has made something that looks like this:
[color=darkcyan]Exec[/color](
When posted that comes out like
Exec(
He has done, (unintentionally, I expect ) , something similar to the “black character trick”: He has done the “dark cyan characters trick” , Lol..
These would be some “black character trick alternatives that will also get over the problem and all would come out in black characters
[color=black]Exec[/color](
Ex[color=black]ec[/color](

E[color=black]xec([/color]

… etc…

If you repost Kyle’s code without the adjustments to the two select occurrences, then it still post with no problems:

Please Login or Register  to view this content.

When I use my tool, ( actually just a slightly modified version of this one: http://www.mrexcel.com/vbaddin.shtml ) things do not look quite so pretty. And I have to add the “black character trick” at the exec to get the code to post:

Please Login or Register  to view this content.

At that problem giving code line in my code above, just before posting, it looked like this:
[color=blue]For[/color] [color=blue]Each[/color] file [color=blue]In[/color] Filter(Split(CreateObject("W Script.Shell").Ex[color=black]ec[/color]("CMD /C DIR """ & startFolder & "*.xl*"" /S /B /A:-D").StdOut.ReadAll, vbCrLf), ".")
This was my workaround:
Ex[color=black]ec[/color](
( I have not made any alterations to the Select occurrences ).

I suppose the moral of the story would be:
Maybe do not use your tool all the time. Give it a rest sometimes. Try it differently sometimes. Maybe try someone else’s, or none at all. Just to see what comes out.

Alan

Thanks for all the input guys, hopefully the OP - and others - will find this useful