You basically do string manipulation, then execute that strong as a line of VBScript code.
One of the many things you'll want to consider is security. Execute statements are prone to code injection. You don't want outside contractors of temporary workers to be able to write statements that gets interpreted by the Execute statement. It's an easy way for them to inject code that is malicious.
I don't want to do a thread hijack here. I use the Execute statement on occasion but I cannot think of how someone would use it in a malicious way.
Oh I thought a second longer and seem to understand it better. The execute statement could be working on data. The data can contain a command to do something dangerous.