I do not have any commercial software to sell.
But FWH undertakes custom commercial projects. As FWH Team member I help development in such cases.
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
I do not have any commercial software to sell.
But FWH undertakes custom commercial projects. As FWH Team member I help development in such cases.
In having Xbrowse most dynamic, I need one more solution :
I can select headers by :
:SetGroupHeader( "Voorbereiding", oBrw[4]:oCol("T1"):nCreationOrder, oBrw[4]:oCol("M4"):nCreationOrder )
But I often refer to the database fields for changing colors.
Can I also use a Xbrowse own option for that ?
oBrw[3]:aCols[1]:bClrStd := { || IF( oRs:selection , { CLR_BLACK,CLR_HGREEN } , { CLR_HRED,CLR_WHITE } ) }
the oRs:selection should become the Xbrowse col, or header, or.... so that I don't have to use the field itself.
nageswaragunupudi wrote:I do not have any commercial software to sell.
But FWH undertakes custom commercial projects. As FWH Team member I help development in such cases.

Marc Venken wrote:nageswaragunupudi wrote:I do not have any commercial software to sell.
But FWH undertakes custom commercial projects. As FWH Team member I help development in such cases.
Is the source included in this kind of project ?
The purpose :
I looking into converting my FW16 to FWH. This can be done, have it partial working, but what I have learned last year with the help of this Forum is
that I don't like my old code a bit. Everything can be done mutch better, easier, nicer,..... So starting from scratch would be best solution.
It is a private project, since i like to create my software by myself, kindy hobby, but start all over is to much work.
Therefore a working project with code as starting point would be perfect.
Ok, there a many samples, but more is needed.