I have finally found it. After switching to new drives, the old problem came up again. I had thought it to be solved by simply copying the db, px amd mb files to another folder.It turns out that only worked because it was a smaller drive, so Footpad was right in his assessment that bde does not recognize large drives. The W2K cd contains the file apcompat.exe. Once installed it can be run for Paradox. Click on drives larger than 2 gb and click on "make these changes permanent". As easy as that.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
The solution to the insufficient Disk Space error.
- Thread starter jlockley
- Start date
- Status
- Thread starter
- #2
TonyMcGuire
Programmer
Is this on installing?
Is this Paradox 7?
Since we haven't all read your past post, maybe clue us in to the whole issue.....????
Tony McGuire
Is this Paradox 7?
Since we haven't all read your past post, maybe clue us in to the whole issue.....????
Tony McGuire
- Thread starter
- #4
Acompat.exe does work. The second error is apparently due to an unrelated issue.
Insufficient disk space is, from my googling, a very frequent problem, which is not related to installation.
Here are two previous posts. The issue,as Footpad explains, is, in fact, not insufficient disk space but Paradox's/DBE's inability to read larger drives. The result is inability to any or all of the following: export, query, restructure or otherwise manipulate tables regardless of actual available space. There may be other issues in force such as cache size or Private folde location. These problems apparently won't exist if the files are located on a drive with less than 2 gb space, but a larger drive with less than 2 gb available space will not work.
This is entirely livable. I also increased the block size in BDE Administrator. I am I have reversed the "make changes permanent" option by restarting acompat.exe and unchecking all but checking "make changes permanent" to reopen Paradox, the closing again and reopening it with acompat.exe. This means that any time I wish to alter a data base, I need to use acompat.exe to open Paradox. fairly sure that this had no influence on the solution, however.
The "number out of bounds" error was resolved by exporting the original file "R.db" to "R1.db", which can be restructured without problem.
I have to add that it took me far too much work to unearth this answer. Obviously Microsoft is aware of the problem inasmuch as they provided a solution. Corel must be similarily informed, so why was no information regarding this simple solution to a very time consuming problem made available? Drives over 2gb were on the market long before Paradox 8 became a legacy product.
Insufficient disk space is, from my googling, a very frequent problem, which is not related to installation.
Here are two previous posts. The issue,as Footpad explains, is, in fact, not insufficient disk space but Paradox's/DBE's inability to read larger drives. The result is inability to any or all of the following: export, query, restructure or otherwise manipulate tables regardless of actual available space. There may be other issues in force such as cache size or Private folde location. These problems apparently won't exist if the files are located on a drive with less than 2 gb space, but a larger drive with less than 2 gb available space will not work.
This is entirely livable. I also increased the block size in BDE Administrator. I am I have reversed the "make changes permanent" option by restarting acompat.exe and unchecking all but checking "make changes permanent" to reopen Paradox, the closing again and reopening it with acompat.exe. This means that any time I wish to alter a data base, I need to use acompat.exe to open Paradox. fairly sure that this had no influence on the solution, however.
The "number out of bounds" error was resolved by exporting the original file "R.db" to "R1.db", which can be restructured without problem.
I have to add that it took me far too much work to unearth this answer. Obviously Microsoft is aware of the problem inasmuch as they provided a solution. Corel must be similarily informed, so why was no information regarding this simple solution to a very time consuming problem made available? Drives over 2gb were on the market long before Paradox 8 became a legacy product.
- Thread starter
- #5
The above got terribly jumbled. It should have read:
I have reversed the "make changes permanent" option. This means that any time I wish to alter a data base, I need to use acompat.exe to open Paradox. This is entirely livable.
I also increased the block size in BDE Administrator. I am fairly sure that this had no influence on the solution, however.
Sorry.
- Thread starter
- #6
Memo to self and anyone else dealing with the NR is out of range issue.
Quick and easy fix (1) remove index (delet .px file)
Slow and dreary fix (2) if removing px file doesn't work, query entire file to a smaller drive (moving doesn't seem to function). Once queried, the file on the smaller drive (see above for reason) can be altered and copied over the original.
How annoying.
Quick and easy fix (1) remove index (delet .px file)
Slow and dreary fix (2) if removing px file doesn't work, query entire file to a smaller drive (moving doesn't seem to function). Once queried, the file on the smaller drive (see above for reason) can be altered and copied over the original.
How annoying.
- Status
Similar threads
- Locked
- Question
- Locked
- Question