Hi Raj,
after having a short exposure to both WD and VC, I think VC can be used for fairly simple applications which you can develop by using tables and forms as the UI elements. The customisation possibilities of VC are thus quite limited.
The main difference between WD and VC is the intended audience of them. VC is aimed at the non-programmers or analysts who just want to quickly model a UI for a BAPI / several BAPI's jointly, for example. With WD you have many more doors open. You can make very customised applications and in general have more control on what you are doing since you're working on the code level.
I think you could find an analogy for the two technologies from the early days of html page development. There were some wysiwyg (what-you-see-is-what-you-get) tools which didn't require you to do any coding but weren't very flexible. Whereas on the other hand, the more serious web developers did their pages by coding straigt html and javascripts on their pages.
So if you have a simple application e.g. for creating sales orders and calling a single bapi, I'd go with VC if there's no customisation. But if you have a bigger sales order tracking tool with different options, I'd go with WD instead.
Bear in mind also that with WD you can create standalone applications on the WAS without needing a portal. So if you are creating apps with VC, they have to be deployed on a portal.
Regards,
MIkko
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.