Questions about changing patches with the soft synths

I'm working on a project right now that is using two soft synths: Cakewalk's DropZone and Camel Audio's Alchemy. I need to be able to change the patches in both synths at certain points during the piece.
 
I think I finally have a handle on doing patch changes with Alchemy, using the Insert>Bank/Patch Change... command, but only for patches that are numbered 127 and lower. I've been struggling with the Banks and Bank Select Method, reading the help files, assigning names, etc, as I read through the various help files, but so far Sonar is not responding the way it seems that it should according to the help files I'm reading, which prevents me from assigning patches that have a number higher than 127. I've also obtained a .pdf of the Alchemy user guide, and it discusses this point as well. But Sonar is not responding to its suggestions, either. I've done the math: the Alchemy users guide explains that you multiply the bank number by 128 and then add the patch number from that bank to the product to determine the new patch value. But the Patch Change pane isn't set up to handle numbers that large. And if I change the value of the bank, it just ignores me. I've even tried editing things in the Event List, trying to insert a patch change there, and even it refuses to cooperate.
 
And then there's DropZone -- and other synths with similar layouts, like Rapture, for example. They both use sort of a drop-down tree arrangement to organize their patches.  I have not been able to figure out what it takes to change patches in DropZone at all. Once a patch is set, it stays set, even when the Event List shows a patch change.
 
Cakewalk points out, in its discussion of DropZone that what Sonar refers to as "patches" are actually what Dropzone calls "programs." Plus, I note that Sonar even has a Patch Browser and DropZone has a Program Browser. Now, it would seem to an ordinary person like me that these two browsers should be able to sync up and share data, since they're both supposedly doing the same thing -- and since they're both pieces of Cakewalk software and all. Wrong. I've been struggling for hours now,  trying all sorts of means and methods to get DropZone and Sonar to agree about patch changes, but still no joy. I can get DropZone to work just fine -- that isn't the issue. Trying to get it to switch patches is what I can't seem to do.
 
So any ideas on how to get DropZone to cooperate, and how I go about referencing patches that are numbered greater than 127?
 

Hi Scook, thanks for the reply. Yes, this is what I'm doing currently, but not because I can't get the synths to load the way I want. I have six occurrences on three tracks that overlap. I guess I'll need to expand the workspace. One of the first things I noticed is that I'm not actually running Alchemy, but Camel Audio's free Alchemy player -- which is not multi-timbral, apparently. I'm overlapping the tracks' voices slightly and the existing voice drops out when the new voice loads.
 
Assuming that full-blown Alchemy is multi-timbral and will work the way I want, I can't afford it at this time, so I'll be looking to use one or more of the free synths I've picked up ( found a bunch at Pluginboutique.com) or one or more of the ones that comes with Cakewalk. Hopefully it will handle at least two versions of itself operating simultaneously.
 
Do you have any recommendations regarding loading synths via the Inset>Bank/Patch Change... with synths that do respond to patch changes, above number 127? I can't get the Bank/Patch Change popup or the Patch Change Browser to do what I need. The Event List won't respond either.