Reinaldo,
>I only want to share information for everyone's benefit.
Benefit for me is judgmental - I think you should use option. Is an option.
Using all those components I came to a point where I had so many unfinished projects and every new release – how long will they support activeX, etc.- were really painful.
>Outlook does not pickup insurance information and will not integrate with my other tables.
There are many examples here how you can interact from FW with outlook which I use.
>Tim got the calendar up and running in two days
I know and made the same experience. But if you need a special feature you can’t overcome if you don’t have the source code.
>Because of an incentive they offered, I did invest in the full library. I'm not sure how much I will use, but time will tell !
This was the same here. you always try more and more and you end with a source code which you can’t handle anymore.
Also to distribute such components is difficult. Sometimes admins don’t let you install the DLLs and OCXs you need.
Especially if you want to show a demo of your software. Then if you install your dlls and ocx files some other programs don’t work any longer because of a version conflict.
>There was a TV ad years ago about car repairs that said "You can pay me now, or you can pay me later." Of course, paying later always ends up costing more.
>Converting to using business classes will save tons of time (and money). Converting legacy applications can best be done a little at a time. As you need to work on specific routines you can start to convert just those routines to objects while leaving other routines untouched.
>There is also a technique called "object wrapping." This is just done by defining a class and encapsulating legacy code into methods of that class. Then as time permits, each method containing legacy code is converted to a true method.
>These techniques can make converting to OOP much less painful and you start to gain some of the productivity of OOP almost immediately.
I am so thankful that James helped me to convert my app to OOP style and having James as a teacher.
My opinion:
If we are fulltime Fivewinners we should try to find solutions using pure Fivewin. Otherwise the advantages this language has are lost.
For example using codejock with VB6 is so much easier than with FIVEWIN all the designers are and debugging is working you could also use
Apollo embedded database engine for managing CA-Clipper files which is working well and the syntax for Apollo is in VB6 similar to xBase.
But VB6 is no longer supported.
If you calculate yours, Tims and James time the money you paid a FW own class would be ready since days.
Best regards,
Otto