But mostly, I suggest leaving it to XBrowse, whether to Refresh() or RefreshCurrent() XBrowse knows it better. Let us not interfere. Now I wonder ..... I think I do some refresh to much then ? Are these refresh OK ? :bChange := { || nSecs := SECONDS(), Scope("factinfo","document","factart","factart"),oBrw[6]:refresh() ...
... different is that the Executable generated with Harbour is a little slower to climb than the executable generated with xHarbour. But, this doesn't interfere in anything and the end user doesn't even notice. No intention of offending anyone, just my humble opinion. A hug. Regards, saludos.
Sorry for the late response. MODAL preview opens a separate window and does not interfere with the MDI window system. This problem is only in the case of NONMODAL previews. This issue is addressed in FWH2007 to be released. You may adopt the same fix in your "rpreview.prg". ...
... to format numeric values. By simply changing the settings of FWNumFormat() you can Internationalize your application as long as you do not interfere with their working by providing your own hard coded picture formats. Hi Mr. Nages, With Xbrowse I try to export to Calc format from LibreOffice ...
XBrowse, TDatarow etc programs automatically use FWNumFormt() settings to format numeric values. By simply changing the settings of FWNumFormat() you can Internationalize your application as long as you do not interfere with their working by providing your own hard coded picture formats.
This is surprising. What we can assure you is that FWH does in no way interfere with the functionality of any RDD (eg DBFNTX,DBFCDX,etc). That is totally handled by (x)Harbour. Strangely you are experiencing problems with 18.05 that were not existing with 1506. ...
... in :oWndClient functioning like a background, so when click the MDIChilds will not go behind. The oMDI:oWndClient will remain active but not interfere with MDIChild behavior and also will not go as Top-Most dialog. any Idea? :?:
... pure SQl treated as above. But I dont know if it is worth while to build such function because you can do it directly from app code and doesn't interfere or take advantage with adordd. Ex //get adordd connection to have it in same transaction processinghb_GetAdoConnection():Execute( ...
... physically built in SQL engine these are only used to build ORDER BY clauses when opening the tables (recordsets) with SELECT.... We should not interfere in the database logic that is for DB ADMIN to do. If later the DB ADMIN gets to the conclusion that many selects are using a certain ORDER ...
Mr Rao, Better we do not interfere with triggers etc. Better to leave it to their database programmers. True I know we shouldnt do it. SELECT `AUTO_INCREMENT` FROM INFORMATION_SCHEMA.TABLESWHERE TABLE_SCHEMA = 'DatabaseName' AND TABLE_NAME ...
... speed? SELECT `AUTO_INCREMENT` FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA = 'DatabaseName' AND TABLE_NAME = 'TableName'; Better we do not interfere with triggers etc. Better to leave it to their database programmers.