I use the Visual FoxExpress framework for all VFP development. I also use the Web Connection framework.
It is very difficult to develop a WC project and then take the code from that WC project and put it into a VFE project. I have done it twice but it is a horrible experience.
It believe would be better to extend my VFE framework by adding the WC framework. Creating VFP applications with VFE (book) explains how to do this in a general way. I have searched the internet all day and when I finally found something that sounds like it might be the answer, it appears the owner of fox wiki got mad at somebody and shut down that website. I was looking for http://fox.wikis.com/wc.dll?Wiki~VFEExtendingTheAbstractFactory~vfp
Does anyone have a copy of that document or can anyone explain how I might add the WC framework to my VFE framework?
Thanks, John
The article is available on the Wayback Machine at: https://web.archive.org/web/20160810180622/http://fox.wikis.com/wc.dll?WikiVFEExtendingTheAbstractFactoryVFP
Hope this helps! Kevin
Not sure what you're doing but you should treat VFE as a business object framework. Create your business objects and then use those business objects in Web Connection and whatever else you use them in (ie. Desktop or COM etc.).
That way you share the business logic, but not the UI. If you're building services especially this is the only way using a framework makes sense. Integrating WWWC into a framework seems like the wrong approach.
+++ Rick ---
Thanks for the link Kevin, John
Rick, You are exactly correct.
As you probably know, using business object in the VFE framework is almost a given. It simply makes database handling so much easier. Having said that I have always had a difficult time separating the business layer from the interface layer. This website project is causing me to realize how important it is to keep them separate. I've always been the "reusable code" person. Even before OOPS, I was known as the macro king. Well, somewhere along the journey, I obviously missed a lesson. In VFE you create a business object for each view. What I only recently realized is that is not really a business object. A true business object would encapsulate many tables/views to accomplish a business task.
Another issue I am facing is that the Point of sale (POS) portion of my app was the whole app when first written in 2.6. It was written to allow 2 users to ring up sales simultaneously on a single workstation, each "side" with it's own barcode scanner and receipt printer and used "call me back" type COM servers so one user never had to wait on the other user, etc. As you can imagine that POS screen was horribly complex and the point of telling all this is that the business logic is very intertwined with the UI. I am in the process of doing as you suggested, separating the 2, no small undertaking.
As always thanks for your support, John