Hi folks,  (Delphi 5, BDE 5.11, Client 98, Server NT 4, Paradox 5+).

How can I prevent, definitily this error? I already readen the document
about oportunistc looking, configure peer-to-peer, upgrade VREDIR and
VNETSUP.VXD.

Sorry about my english wrong,

Regards,

Gustavo Tortorelli - Brazil

Paradox-5 (16-bit) is probably not the wisest choice to use ... also
note that it isn't going to be using your BDE 5.11 anyhow.  You could be
mixing 16-bit and 32-bit code in the same environment and this is not
wise.  Upgrade to Paradox-9 or so (http://www.corel.com).

--
------------------------------------------------------------------
Sundial Services :: Scottsdale, AZ (USA) :: (480) 946-8259
mailto:i...@sundialservices.com  (PGP public key available.)

Another possibility is that the index-files could be US-Ascii while the
database file is in a national language.  This can cause "an index that
goes out of date instantly."  

ChimneySweep? (with repair turned off) is a reliable way to determine if
the table header really -is- corrupt and if the index really -is- out of
date with respect to the data.

--
------------------------------------------------------------------
Sundial Services :: Scottsdale, AZ (USA) :: (480) 946-8259
mailto:i...@sundialservices.com  (PGP public key available.)

Are you certain that you have Local Share set to True on _every_ computer?

--
Bill

Yes, Ive,

I readen articles TI3342 & Co..

I guess that problem occurr when the client machine turn down with system
active.

Gustavo

"Bill Todd (TeamB)" <b...@nospamdbginc.com> escreveu na mensagem
news:3a3fb445$1_1@dnews...

Hi again,

Now, I discover new problem. When I receive message about index out of date
about table PARADOX with 3 fields FMTMEMO, after recover with, I lost
contents from this fields.

To repair, I used DBEXPL32.exe, demo application from RXTOOLS 2.75 that use
TUTIL32.DLL.

Remember, I use BDE 5.01.

Help please.

Gustavo
(sorry english wrong)
"Bill Todd (TeamB)" <b...@nospamdbginc.com> escreveu na mensagem
news:3a3fb445$1_1@dnews...

You might want to look for network problems such as a bad NIC or hub. My
experience has been that Paradox tables are quite stable in a multi-user
environement if the BDE is configured correctly and the network is stable.

--
Bill

Hi

Try this

On the Win98 Clients disable new file sharing and locking semantics.

Control Panel/System/Performance/File System/Troubleshooting/  then just
tick the box.

It worked for me, assuming you actually turned off "opportunistic Locking"
on the server.

Merry Christmas

John.

You need a UPS on every machine whether they are clients or
server.
And make sure you close all files before the last form of
the application closes.  This seems to give the bde an extra
second to shut  things down properly.  Also, Novell Netware
seems to be better for Paradox files then NT.  We have 20
users pounding on a delphi paradox file application and
rarely have problems.

"Tortorelli,Gustavo" <gust...@optionsnet.com.br> wrote in
message news:3a3f305c_2@dnews...

In my experience it is NT that is to blame. Novell is probably the best
solution in terms of secutiry and speed, but you could try hosting the data
on a 98 server - it works fine and no corruption.

Jascha