This problem is occur only with adsdbe without all runs well.
We have ads 126.96.36.199 installed on server.
Our program use one dbf (here named DBMAIN) to exchange information with
other programms and store main values.
This DBMAIN is open shared for read in all programs and is never closed -
only on exit.
In this program we start a calculation routine in a new thread.
The calculating thread change some values in DBMAIN an then ends the thread.
All programs running at this time shows the old values from DBMAIN ! On all
workstations at the same time!
The changed values only appears, when we close and re-open DBMAIN or we do
The user didnt wait for automatic data refresh, they work on with the
program or press the update key.
the DBMAIN has only one record. All programms points to this record, ever
(so DBMAIN has no index).
The problem was unnoticed long time - we built in the calculating thread one
We can test the different results by switching on/of using adsdbe.
There must be a difference in using adsdbe and pure xbase++
Did someone know this problem?
Subject: problem with adsdbe: thread change field value but other active threads view old value!
Date: Sun, 25 May 2008 12:09:47 +0200
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-Trace: 25 May 2008 04:03:58 -0700, 188.8.131.52
Xref: solutions.advantagedatabase.com Advantage.Xbase++:960
Article PK: 1140806
From: UliTs <ProScope@t-online.de>
User-Agent: Thunderbird 184.108.40.206 (Windows/20080914)
Subject: Re: problem with adsdbe: thread change field value but other active threads view old value!
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
X-Trace: 3 Nov 2008 02:36:36 -0700, 220.127.116.11
Xref: solutions.advantagedatabase.com Advantage.Xbase++:1002
Article PK: 1140846
every time you want to read the actual values from the same record
you have to use dbskip(0)!
The old adsdbe was not optimized and much slower.
Roland Gentner schrieb: