FiveTech Software tech support forums

... Note: Dbl-click to open edit screen is not a feature of basic xbrowse. It is a functionality provided by xbrowser. We can disable it as I have advised in the code.

... NOT a Problem of CLASS TPQServer(), it is METHOD SavePQQ() of Fivewin SavePQQ() is a method of TDataRow class of FWH. That is the reason, why we advised not to use TDataRow and other FWH functions for reading, editing and modifying the PostGre records and instead directly use TPQquery and TPQrow ...

Our FWH maria library initially connects to the server with MYSQL_OPT_RECONNECT option. As many other users advised, time out or sleeping and any such reasons are irrelevant. Even if timed out, any communication with the server ( eg even a simple oCn:Ping() ) will automatically ...

1. Download and install ODBC driver as advised above. 2. You need not worry about connection string. FWH functions will automatically and transparently do it for you. oCn := FWOpenAdoConnection( { "MYSQL", <serveraddress>, ...

Posted using https://postimage.org advised by Mr. Cristobal

Tim, Be advised that most, if not all, of your customer's probably don't have the hardware required to run Windows 11. Microsoft has relaxed some of the requirements, but hardware still requires some of the latest and most powerful ...

En cuanto a la recomendación de Rao me lanza este error: I advised oBrw:NUM_LIB:cSortOrder := "DOCFECHA"  because in your sample, NUM_LIB was the header of the first column. oBrw:NUM_LIB means the column which has the header "NUM_LIB". ...

Because oImage:Save( .t., ... ) is working, you do not need to copy and paste to TBitmap/TImage object. We also advised not to do it. In other words, you totally remove "oImage:CopyToClipBoard( .T. ), GuardarGraficaClinica( oImage, aImages )" and instead use oImage:Save() ...

Because oImage:Save( .t., ... ) is working, you do not need to copy and paste to TBitmap/TImage object. We also advised not to do it. In other words, you totally remove "oImage:CopyToClipBoard( .T. ), GuardarGraficaClinica( oImage, aImages )" and instead use oImage:Save() ...

You can open as many tables as you want simultaneously. Use different variable names for different tables, like Mr. Armando advised. Eg oRsCust := oCn:RowSet( "select * from customers" ) oRsSale := oCn:RowSet( "select * from sales" ) You need not switch the rowsets ...

... is displayed //If uNew is imagefile or resource,etc this image is displayed on record //selector in the place of the standard right arrow. //Advised to specify bitmap with size 16x16 or less . oBrw1:bClrSelFocus := { || { 0, 14540287 } } oBrw1:bClrSel := { || { 0, 15132365 } } oBrw1:nRecSelColor ...

... In the old school of programming (of thought) of the old clipper from the Autumn 86 - Summer 87 version passing through DBIII , my friends always advised me not to make an archive with many fields but to make many archives with few fields and now I really don't know if this solution is decisive ...

... each package (element + service). I have not found solutions. for me only in this way the user could customize each price because doing as I was advised some time ago by the experts you risk not calculating the right rate well

... summer season for all the services was a huge mistake: 10 elements X 10 services X 10 packages X 10 sections X 93 days = 930,000 price records he advised me to create a small archive with the prices per day / week / 15days / month as described in the price list that the owner of the chalet gave ...

Still, we advise you to adopt the approach and syntax advised by us in our samples above. They are safe and work with any database. You will not be wasting your time in searching for solutions like this.