index corruption dbfntx - xharbour

Hey Detlef,

> long time i hesitated to migrate our main sales program to xHarbour.
> Now i did it and the system suffers by index corruption :-(

Sorry to hear Detlef. In my app its just the opposite. Since I moved to
xHarbour, I had NON Index corruptions while in Clipper, it was almost
every week..

I use RMDBFCDX now in xHarbour.

> In our network 2 users are using the new xHarbour version of our sales
> program and 4 others still the old DOS version.

Can you try to use separate indexes for your xH compiled app. Just to
see if it has something to do with joined usage by Clipper and xHarbour
of the NTX files?

--
Sincerely,

Patrick Mast,
xHarbour.com Inc.
http://www.xHarbour.com

Patrick Mast schrieb:
> Hey Detlef,
>
>> long time i hesitated to migrate our main sales program to xHarbour.
>> Now i did it and the system suffers by index corruption :-(
>
> Sorry to hear Detlef. In my app its just the opposite. Since I moved to
> xHarbour, I had NON Index corruptions while in Clipper, it was almost
> every week..
>
> I use RMDBFCDX now in xHarbour.
>
>> In our network 2 users are using the new xHarbour version of our sales
>> program and 4 others still the old DOS version.
>
> Can you try to use separate indexes for your xH compiled app. Just to
> see if it has something to do with joined usage by Clipper and xHarbour
> of the NTX files?
>

Hi Patrick,

thanks for your advices.
I already wrote several xHarbour/FWH programs which are working without
trouble.
But our sales program is a console app and drives me crazy.
When switching quickly between screens made with ct.lib the program
suddenly closes and wants to send a problem report to Microsoft.
That's the reason why not everybody is using the xHarbour version in our
office.

Separate index files is not possible because all user must share the
same data. I'll consider about this in a special test environment where
i hope to find more hints.

Did you ever heard if the xHarbour dbfntx rdd has problems with for
clauses in indexes?

Regards,
Detlef

Dear Detlef Hoefner:

"Detlef Hoefner" <hoefner@odn.de> wrote in message
news:fcvsus$dmj$00$1@news.t-online.com...
> Hi all,
>
> long time i hesitated to migrate our main sales
> program to xHarbour. Now i did it and the
> system suffers by index corruption :-(
>
> In our network 2 users are using the new
> xHarbour version of our sales program and 4
> others still the old DOS version.
>
> The old version NEVER had dbfntx 1210 errors
> over the last 14 years. I use the following
> settings im my programs:
>
> xHarbour :
> SET DBFLOCKSCHEME TO 2
> HB_LANGSELECT( "DE" )
> HB_SETCODEPAGE( "DE" )
>
> Cliper 5.2e :
> linked with NTXLOCK2.OBJ and CTGR.OBJ
>
> Could anyone tell me if i'm missing something?

Check the documentation. Clipper 5.2 requires DBFLOCKSCHEME to
be 1. The value of 2 is for Clipper 5.3. Maybe that is all it
is...

David A. Smith

Hello Detlef,

> Did you ever heard if the xHarbour dbfntx rdd has problems with for
> clauses in indexes?

No reports on this no.

--
Sincerely,

Patrick Mast,
xHarbour.com Inc.
http://www.xHarbour.com

N:dlzc D:aol T:com (dlzc) schrieb:
> Dear Detlef Hoefner:
>
> "Detlef Hoefner" <hoefner@odn.de> wrote in message
> news:fcvsus$dmj$00$1@news.t-online.com...
>> Hi all,
>>
>> long time i hesitated to migrate our main sales
>> program to xHarbour. Now i did it and the
>> system suffers by index corruption :-(
>>
>> In our network 2 users are using the new
>> xHarbour version of our sales program and 4
>> others still the old DOS version.
>>
>> The old version NEVER had dbfntx 1210 errors
>> over the last 14 years. I use the following
>> settings im my programs:
>>
>> xHarbour :
>> SET DBFLOCKSCHEME TO 2
>> HB_LANGSELECT( "DE" )
>> HB_SETCODEPAGE( "DE" )
>>
>> Cliper 5.2e :
>> linked with NTXLOCK2.OBJ and CTGR.OBJ
>>
>> Could anyone tell me if i'm missing something?
>
> Check the documentation. Clipper 5.2 requires DBFLOCKSCHEME to
> be 1. The value of 2 is for Clipper 5.3. Maybe that is all it
> is...
>
> David A. Smith
>
>
Thanks, David.
I'll give it a try.

Regards,
Detlef