Sorry I meant I am trying to attach a screen shot
 

All I know is VST 3 has fixed a problem with Melda plugins for me. 

Thanks Noel I think that was where I was going wrong I was expecting to see the sidechain input within the plugin as below
 

SONAR has always considered sidechains from the point of view of what you want to route to the sidechain - i.e. the sending track or bus. Users of some other steinberg DAW's are used to seeing sidechain from the point of view of the plugin and picking the source from there. Its just a matter of semantics. 
 
Personally I find it more natural from a routing point of view to think of it from what you are sending to the sidechain. However since some users prefer to look for it at the plugin level, we may consider adding a sidechain picker to the UI in the future.

When you switch between DAWS it is sometimes good to have some commonality between them, that's where it tripped me up.  I hear what you are saying about routing but to me it makes more sense to have a common standard for VST integration as it is a standard that is here to stay.  For example, as shown below, how can I automate all the parameters in Nexus with sonar?  I have no icons for  recording and controlling / automating the changes to the parameters as I do in all the other DAW's I use
 

That is a 32bit plug-in running in BitBridge. To view the standard VST header, hold the SHIFT key when opening the plug-in UI. The header usually will open behind the plug-in so it may be necessary to move the plug-in to see it. The automation controls are also on the track.

Scook...you tha man!  Thanks a LOT!!!!!

Thanks for all the feedback, looks like the water is fine except for what appear to be some small things that cake and waves are working out and I'll be getting in soon.