To: fwienk@dds.nl (Frank Wienk)
Subject: internal error 5333
Hi boys,
FW>>	DBSETINDEX(0) internal error 5333
FW>>Does anybody know what it means?
FW>>Thank you.
FW>>Dario.
FW>Hi there,
FW>Some time ago, I had the same problem. It finally turned out to be a
FW>bug in the RDD-driver I used. After a re-index the problem was gone,
FW>but the next day (or a few day's later) it came back. Over and over
FW>again! This went on for weeks, with a total index-rebuild almost every
FW>day. I thought I was going crazy. I was using the NSX52 driver (yes,
FW>the freeware version 1.1: BIG mistake, VERY VERY BIG mistake). One
FW>day, I changed everything back in NTX indexfiles. The problem was gone
FW>forever, NEVER to be seen again...
I've killed this problem forever using all areas indexed in "DBFCDX"
( .OR. FoxPro format index). Faster, MUCH smaller and better. You
create only one index file with many orders inside, creating one
symbol in the table.
Try to use VIA "DBFCDX" and I'm sure you'll have this trouble
finished. Don't forget to link the dbfcdx.lib and put REQUEST DBFCDX
on top of prgs.
Let me know if you succeed.
[]s
Andre Khury
akhury@painet.com.br
--- FMail/386 1.02
---------------