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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
"Insufficient Disk Space" When changing structure 1
- Thread starter jlockley
- Start date
-
1
- #2
NotAllThere
Technical User
Check the BDE setup, particularly Block Size, for Paradox tables. Go to BDE Administrator, Configuration Tab, Configuration, Drivers, Paradox and review Block Size and other parameters. Make sure to note existing values before making changes. I suggest to make only one change at a time and check the effect.
You might also want to check on the Paradox/BDE limits, see
(155 fields...<grin>)
HTH.
You might also want to check on the Paradox/BDE limits, see
(155 fields...<grin>)
HTH.
- Thread starter
- #3
Thank you
I tried, but no success so far. BDA ADM shows the internal version as 4. How would I ascertain this? Using the settings in help, I changed block size from 2048 to 4096 with no result.
I experimented by borrowing the structure for a new table, and was able to change that, so it's the old one that won't budge. Any thoughts? I suppose I can querry the old one ove, but that's a lot of fields to deal with.
I tried, but no success so far. BDA ADM shows the internal version as 4. How would I ascertain this? Using the settings in help, I changed block size from 2048 to 4096 with no result.
I experimented by borrowing the structure for a new table, and was able to change that, so it's the old one that won't budge. Any thoughts? I suppose I can querry the old one ove, but that's a lot of fields to deal with.
- Thread starter
- #4
- Thread starter
- #5
- Thread starter
- #7
- Thread starter
- #10
Great minds do think alike. I already did that and got the same message. It's only this table. I reinstalled Paradox and still got the same message. I am now in the process of attempting to export the same table via a Query. Wish me luck.
What possible connection could there be on this? I just can't find anything I can delete or jetison that could be doing this. The table is about 40 mgs and the object file is about 220 megs. I don't find anything about those limits in the Limits list.
Update. The query seems to have worked. I am right now saving it after reinstalling the key. When that is done I will try to insert the desired object field, then get back with the results. Thanks again for the help. I'll let you know.
What possible connection could there be on this? I just can't find anything I can delete or jetison that could be doing this. The table is about 40 mgs and the object file is about 220 megs. I don't find anything about those limits in the Limits list.
Update. The query seems to have worked. I am right now saving it after reinstalling the key. When that is done I will try to insert the desired object field, then get back with the results. Thanks again for the help. I'll let you know.
- Thread starter
- #11
Riddle me further: At this point all seems succesful. Number of records and number of fields are the same. What is odd, though, is that the actual table is just about 4mb smaller, while the mb file has gained about 12 mb. Go figure. Obviously there is something corrupted somewhere, but it's beyond my capacity to guess what.
I have experienced problems with memo fields in version 8. Never this exact problem, but GPFs and other issues. So far I have determined that the TAB character seems to play some role. Just a thought.
Mac
"There are only 10 kinds of people in this world... those who understand binary and those who don't"
langley_mckelvy@cd4.co.harris.tx.us
Mac
"There are only 10 kinds of people in this world... those who understand binary and those who don't"
langley_mckelvy@cd4.co.harris.tx.us
- Thread starter
- #13
Please note that Table Repair does not identify or fix all type of table corruptions.
Exporting and importing data are usually the next steps.
Pdox 8 was not a stable version. I have had other problems with it and had quickly upgraded it to Pdox 9.
If you continue have problems, may be you would like to consider an upgrade.
Exporting and importing data are usually the next steps.
Pdox 8 was not a stable version. I have had other problems with it and had quickly upgraded it to Pdox 9.
If you continue have problems, may be you would like to consider an upgrade.
- Thread starter
- #15
I would if it were still available. I tried oem version of 10 (no oem, but it seemed a pretty simple way to check to see if I like it) and had enormous problems. Perhaps I will get another copy and retry or try for 9 on line.
What are the other benefits of 9 and 10?
What are the other benefits of 9 and 10?
jlockley,
Most of the major changes between 8, 9, and 10 are internal. Rumor has it Corel changed the compiler and that fixed a lot of memory leaks. We've also heard that they focused on many printing problems over the past couple of years, that's not only faster, but more reliable.
v10 does have a new feature called stringlists, which appears to offer a lot of poential for code reduction in applications, though I confess I've not had time to study them extensively yet.
Other than that, the UI's changed quite a bit. It's a little cleaner is some ways and more in annoying in others (at least to me, who was weaned on pre-release versions of Paradox 1.0).
Also, they've added little bits here and there, such as tooltip properties and other small adjustments.
Oh, one thing in v10 does make it worth the investment in my book: Since you can now only obtain Paradox 10 via WPO 2002/Pro, they added Paradox Runtime to the overall package, which means it's no longer an extra $500-600 purchase. Very handy for redistributing database apps internally.
Hope this helps...
-- Lance
Most of the major changes between 8, 9, and 10 are internal. Rumor has it Corel changed the compiler and that fixed a lot of memory leaks. We've also heard that they focused on many printing problems over the past couple of years, that's not only faster, but more reliable.
v10 does have a new feature called stringlists, which appears to offer a lot of poential for code reduction in applications, though I confess I've not had time to study them extensively yet.
Other than that, the UI's changed quite a bit. It's a little cleaner is some ways and more in annoying in others (at least to me, who was weaned on pre-release versions of Paradox 1.0).
Also, they've added little bits here and there, such as tooltip properties and other small adjustments.
Oh, one thing in v10 does make it worth the investment in my book: Since you can now only obtain Paradox 10 via WPO 2002/Pro, they added Paradox Runtime to the overall package, which means it's no longer an extra $500-600 purchase. Very handy for redistributing database apps internally.
Hope this helps...
-- Lance
- Thread starter
- #17
dfriend846
Technical User
I don't have any reason for your problem but I have found the same thing using Pdx 10 and a large dataset. Our cure was to save the data we wanted and add it to a new dataset then rename it to the old name. This seemed to work. We surmised it was due to the size of the dataset. Things that did not work along the way were verifying the table, updating it to the latest form (our data went back to Pdx 4 and we updated versions periodically).
Dennis
Dennis
- Thread starter
- #19
jlockley,
Dataset is a general term for table, answer table, or similar collection of records. It's a term borrowed from the VCL of Borland Delphi. In SQL terms, "cursors" and "tuples" are vaguely similar.
Hope this helps...
-- Lance
Dataset is a general term for table, answer table, or similar collection of records. It's a term borrowed from the VCL of Borland Delphi. In SQL terms, "cursors" and "tuples" are vaguely similar.
Hope this helps...
-- Lance
- Status
Similar threads
- Locked
- Question