|
Post by Xifar on Jun 1, 2019 12:30:13 GMT 1
hello first of all i want to thank you for this work
here are some problems I encountered
when I reindex a small database with vdos everything works fine, unfortunately this same database when I want to exploit in network with msdos I have index problems.
in the big databases I always have the problem "Error _dbfcdx/1021 data width error"
I think there is a problem in managing indexes
I also noticed that I can not leave the application, I have to do alt + c to exit
note that the only change in autoexec is
set clipper = f248
I use the version vDos 2019.05.01, Win 10 64
forgive my english
|
|
|
Post by Jos on Jun 1, 2019 15:33:52 GMT 1
How to exit differs per DOS application. It’s just ALT+C in your application?
For any comments to your index problems, I would need some setup to test and instructions how to replicate those errors.
Jos
|
|
|
Post by Xifar on Jun 2, 2019 15:59:32 GMT 1
I will try to bring more precision - the reindexing of the database passes successfully, on a registration number of 605000 - the search for invoices works if the number is less than 80232 record, if it is superior, nothing is displayed - the display of line bills works if the number is less than 99580 record, if it is higher I have a systematic error Error _dbfcdx / 1021
another tests - with a database of small size on the network if I reindex with vdos the posts with vdos march against the posts with win xp msdos I have error _dbfcdx / 1021
and finally - when I am at the main menu of the application I have to press 999 to leave the application cleanly with msdos it works well, with vdos nothing happens
|
|
|
Post by Jos on Jun 2, 2019 16:34:07 GMT 1
Although more details, that still doesn’t help. I would need to have a look ‘under the hood’ of your program, how its internal workings causes the different behavior.
Jos
|
|
|
Post by herman on Jun 4, 2019 10:29:46 GMT 1
Sounds familiar to me also at dBase van Borland. Reindex completes new data order, but does not remove the old one from the index. This may corrupt the index. Re-creating index (s) completely is the only remedy. Also related to the problem is that data is not written directly to drive. In dBase, AUTOSAVE had to be on (SET AUTO ON) for proper handling.
If you do not do this, then the data will not be released in time for further use
Herman
|
|