The first step one should take when writing a script (or any program, for that matter) is collect your thoughts on what it is you want the script to do for you. You should write down the general sequence of things in "plain English". For example, let's suppose you want to write a mailrun script. Your initial cut at the process might look like this on a sheet of paper (or text file): WHAT I WANT MY SCRIPT TO DO ~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Select which BBS(s) to call 2. Dial those BBSs in sequence 3. Logon to each board after a successful connection 4. Go to the mail door 5. Upload/Download mail 6. Logoff As you can see, several of these categories are very broad in nature and will probably require expansion..that's ok. The purpose of the first step is to prepare you for the next step which is: FLOWCHARTING. END OF LESSON #1 Preview of coming attractions: Lesson #2: Flowcharting, Lesson #3: Pseudocode, Lesson #4 - ?: Coding the program, Lesson #?+1: Testing the program, Lesson #?+2: Debugging the program NOTE: I am going to assume that you (and anyone else who's interested in learning something here) will take the initiative to become familiar with the {COMMO} macro commands..consider that your "homework"... I will provide lessons on how to actually *use* the commands. I don't want to get into discussing command syntax, though (other than as a debugging aid), since that aspect is covered well already by the COMMO macro language docs.. Jim