Like Hhatkin said, most of the extra commands, specially the discrete ones, are added by users. Since most OEM remotes don't have discrete commands (because they would take too much button space on the OEM remote), most discrete commands are added by users via a Pronto code with fingers crossed. If the added command did not work, then there is no provision to delete it. One has to wait for the database police to clean up the mess. Also, some commands may work only on newer models or work differently on some models. That is why it's important for you to document the behaviour of the commands for you particular model. If you find that many discrete commands work, then use the discrete method (Method 2) along with adding one or more InputNext command(s) in the Activity Start macro feature when needed. Always look for the nearest discrete command requiring the least amount of InputNext. If you find that nearly none of the discrete commands work, then maybe you should select the cycling method (Method 1), but with method 1 (cycling), make sure the number and order of inputs are correct and answer all the questions properly.