... only for indexed DBF, when an index is selected. i do NOT use any Index and that OEM DBF have no *.CDX i "just" play with "SET DBFLOCKSCHEME" and suddenly "Increment" is active (how to disable Increment ? ) :?
Yes yes I use it with both, I have not found any problem. I use this config REQUEST DBFCDX rddsetdefault( "dbfcdx" ) REQUEST DBFFPT SET DBFLOCKSCHEME TO 2 // clp53 REQUEST HB_LANG_IT HB_LANGSELECT( 'IT' ) #ifndef __XHARBOUR__ request HB_CODEPAGE_ITWIN set( _SET_CODEPAGE, "ITWIN" ...
... SET CONFIRM........: OFF SET CONSOLE........: ON SET COUNT..........: 0 SET CURSOR.........: 1 SET DATE FORMAT....: MM/DD/YY SET DBFLOCKSCHEME..: 0 SET DEBUG..........: OFF SET DECIMALS.......: 2 SET DEFAULT........: SET DEFEXTENSIONS..: ON SET DELETED........: OFF SET DELIMCHARS.....: ...
... SET CONFIRM........: OFF SET CONSOLE........: ON SET COUNT..........: 0 SET CURSOR.........: 1 SET DATE FORMAT....: MM/DD/YYYY SET DBFLOCKSCHEME..: 0 SET DEBUG..........: OFF SET DECIMALS.......: 2 SET DEFAULT........: C:\FOX\SALITE SET DEFEXTENSIONS..: ON SET DELETED........: ON ...
... REQUEST HB_LANG_LT REQUEST HB_GT_GUI ANNOUNCE RDDSYS REQUEST DBFCDX function Main() SET DATE FORMAT TO "YYYY.MM.DD" SET DBFLOCKSCHEME TO 2 set( _SET_CODEPAGE, "LTWIN" ) set( _SET_LANGUAGE, "LT" ) ... Maybe also it's needful to convert labels with Fwh ...
... REQUEST HB_LANG_LT REQUEST HB_GT_GUI ANNOUNCE RDDSYS REQUEST DBFCDX function Main() SET DATE FORMAT TO "YYYY.MM.DD" SET DBFLOCKSCHEME TO 2 set( _SET_CODEPAGE, "LTWIN" ) set( _SET_LANGUAGE, "LT" ) ... Maybe also it's needful to convert labels with Fwh ...
Function xHBRddInit() REQUEST DBFCDX REQUEST DBFFPT dbSetDriver("DBFCDX") SET DBFLOCKSCHEME TO 3 RETURN NIL I had some problems like yours up to time when I wrote this line SET DBFLOCKSCHEME TO 3[/quote] Wow ! Interesting ! Here is mine : ANNOUNCE RDDSYSREQUEST ...
... ) // hb_langselect('PLWIN') REQUEST HB_CODEPAGE_PL852 REQUEST HB_LANG_PL852 hb_SetCodepage( "PL852" ) hb_langselect('PL852') SET DBFLOCKSCHEME TO 3 RETURN NIL I had some problems like yours up to time when I wrote this line SET DBFLOCKSCHEME TO 3
... SET CONFIRM........: ON SET CONSOLE........: OFF SET COUNT..........: 0 SET CURSOR.........: 1 SET DATE FORMAT....: DD/MM/YYYY SET DBFLOCKSCHEME..: 0 SET DEBUG..........: OFF SET DECIMALS.......: 2 SET DEFAULT........: SET DEFEXTENSIONS..: ON SET DELETED........: ON SET DELIMCHARS.....: ...
Richard, Thanks for you info. But as you can see in the test-program, the programs slows-down even without locking records, so I think DBFLOCKSCHEME will not make it faster. Its strange that it runs very fast on the network if only 1 person use the program. So I think it's not because a virus-scanner ...
... this can be acheived using OS_NETREGOK( .T. ) Anti virus has to be tuned, it can be a nightmare also One thing that may help is to tune the DBFLOCKSCHEME , this has improved performance in our case SET DBFLOCKSCHEME TO 2 is what we use, you can find on xharbour's doc all the different parameters ...
... that I'd try to avoid as much as possible as the RDDs are developed by totally different group of people. If you can't avoid it, take note of SET DBFLOCKSCHEME command. You can refer to xHarbour's documentation for a detailed explanation about it. Hope that helps.
this remembers me to my errors. I'm using 16 bit and 32 bit programs together and i got rid of this problems by linking ntxlock2.obj to my 16 bit applications and using "SET DBFLOCKSCHEME TO 2" in my xHarbour code.
Robert, i use a mixed system of Clipper 5.2e programs ( comix and dbfntx files ) together with xHarbour's dnfntx and dbfcdx. I also set SET DBFLOCKSCHEME TO 2 But for my Clipper apps i added "FI NTXLOCK2" to my link script. Without i had some troubles with error dbfntx 1012 index corruption. ...