DbUseArea: index file not opened on slow network

#1 08-25-2008, 01:26 PM

Hi,

in a slow network environment (2 Mbit/s) DbUseArea() does not open the
corresponding index file.
I get the error "DBFCDX/1201 - Workarea not indexed" when I try to
call DbSeek().
The same code works on any network with normal speed.

Has anybody a idea why this happens?

Best regards, Timm.

#2 08-25-2008, 03:11 PM

Dear Sodtalb...:

On Aug 25, 10:26*am, Sodtalb...@googlemail.com wrote:
...
> in a slow network environment (2 Mbit/s)
> DbUseArea() does not open the corresponding
> index file. I get the error "DBFCDX/1201 -
> Workarea not indexed" when I try to
> call DbSeek(). The same code works on any
> network with normal speed.
>
> Has anybody a idea why this happens?

Please confirm that none of these operations helps:
... making sure that autopen is on.
SET AUTOPEN ON
... seeing if explicitly requiring the index file changes the result
USE <cFilename> INDEX <cFilename>
... seeing if the index is not "turned on".
SET ORDER TO 1

Really hard to diagnose without a reduced self-contained program
sample that shows the problem.

David A. Smith

#3 08-25-2008, 03:29 PM

2 Mbits/s sounds as if it might be a wireless connection.

xHarbour/Clipper/xBase/FoxPro/Harbour and NOT client-server
architecture, and as such it is very dangerous to try to run
applications over a wireless connection. You would be courting major
possibilities of data and/or index corruption.

If you are connecting wirelessly, please reconsider.

Sodtalbers@googlemail.com wrote:
> Hi,
>
> in a slow network environment (2 Mbit/s) DbUseArea() does not open the
> corresponding index file.
> I get the error "DBFCDX/1201 - Workarea not indexed" when I try to
> call DbSeek().
> The same code works on any network with normal speed.
>
> Has anybody a idea why this happens?
>
> Best regards, Timm.

#4 08-25-2008, 03:41 PM

Correction, I should have said that those applications ARE not
client-server.

Tim Jacob wrote:
> 2 Mbits/s sounds as if it might be a wireless connection.
>
> xHarbour/Clipper/xBase/FoxPro/Harbour and NOT client-server
> architecture, and as such it is very dangerous to try to run
> applications over a wireless connection. You would be courting major
> possibilities of data and/or index corruption.
>
> If you are connecting wirelessly, please reconsider.
>
>
>
> Sodtalbers@googlemail.com wrote:
>> Hi,
>>
>> in a slow network environment (2 Mbit/s) DbUseArea() does not open the
>> corresponding index file.
>> I get the error "DBFCDX/1201 - Workarea not indexed" when I try to
>> call DbSeek().
>> The same code works on any network with normal speed.
>>
>> Has anybody a idea why this happens?
>>
>> Best regards, Timm.

#5 08-26-2008, 10:14 AM

On Aug 25, 4:41*pm, Tim Jacob <tja...@nospam.jollyfarmer.com> wrote:
> Correction, I should have said that those applications ARE not
> client-server.
>
>
>
> Tim Jacob wrote:
> > 2 Mbits/s sounds as if it might be a wireless connection.
>
> > xHarbour/Clipper/xBase/FoxPro/Harbour and NOT client-server
> > architecture, and as such it is very dangerous to try to run
> > applications over a wireless connection. *You would be courting major
> > possibilities of data and/or index corruption.
>
> > If you are connecting wirelessly, please reconsider.
>
> > Sodtalb...@googlemail.com wrote:
> >> Hi,
>
> >> in a slow network environment (2 Mbit/s) DbUseArea() does not open the
> >> corresponding index file.
> >> I get the error "DBFCDX/1201 - Workarea not indexed" when I try to
> >> call DbSeek().
> >> The same code works on any network with normal speed.
>
> >> Has anybody a idea why this happens?
>
> >> Best regards, Timm.- Hide quoted text -
>
> - Show quoted text -

Hi Tim
Which product are you creating the index with and which one generates
the "not indexed" error ?
I used to see situations where, for example, an index created with
xHarbour and opened with Fox generated that same error while working
perfectly with Clipper.
Probably has nothing to do with the lan speed.
HTH
Claudio

#6 08-27-2008, 06:16 AM

Hi David,

AUTOPEN is set to ON and I use SET ORDER TO 1 after calling
DbUseArea()

Best regards, Timm.

On 25 Aug., 21:11, dlzc <dl...@cox.net> wrote:
> Dear Sodtalb...:
>
> On Aug 25, 10:26*am, Sodtalb...@googlemail.com wrote:
> ...
>
> > in a slow network environment (2 Mbit/s)
> > DbUseArea() does not open the corresponding
> > index file. *I get the error "DBFCDX/1201 -
> > Workarea not indexed" when I try to
> > call DbSeek(). *The same code works on any
> > network with normal speed.
>
> > Has anybody a idea why this happens?
>
> Please confirm that none of these operations helps:
> ... making sure that autopen is on.
> SET AUTOPEN ON
> ... seeing if explicitly requiring the index file changes the result
> USE <cFilename> INDEX <cFilename>
> ... seeing if the index is not "turned on".
> SET ORDER TO 1
>
> Really hard to diagnose without a reduced self-contained program
> sample that shows the problem.
>
> David A. Smith

#7 08-27-2008, 06:19 AM

Hi Tim,

the connection is not wireless. A very slow telephone network cable is
in use.
Everything works except the index files.

Best regards, Timm.

On 25 Aug., 21:29, Tim Jacob <tja...@nospam.jollyfarmer.com> wrote:
> 2 Mbits/s sounds as if it might be a wireless connection.
>
> xHarbour/Clipper/xBase/FoxPro/Harbour and NOT client-server
> architecture, and as such it is very dangerous to try to run
> applications over a wireless connection. *You would be courting major
> possibilities of data and/or index corruption.
>
> If you are connecting wirelessly, please reconsider.
>
>
>
> Sodtalb...@googlemail.com wrote:
> > Hi,
>
> > in a slow network environment (2 Mbit/s) DbUseArea() does not open the
> > corresponding index file.
> > I get the error "DBFCDX/1201 - Workarea not indexed" when I try to
> > call DbSeek().
> > The same code works on any network with normal speed.
>
> > Has anybody a idea why this happens?
>
> > Best regards, Timm.

#8 08-27-2008, 06:22 AM

Hi Claudio,

I use xHarbour for both index creation and opening.

Best regards, Timm.

> Which product are you creating the index with and which one generates
> the "not indexed" error ?
> I used to see situations where, for example, an index created with
> xHarbour and opened with Fox generated that same error while working
> perfectly with Clipper.
> Probably has nothing to do with the lan speed.
> HTH
> Claudio

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode