Hi there

I have a photo database with 3000 records and 1.5 GB mb file, and some
forms, reports and a query.

one of the text fields is to short 26 carracters need to be 30 but
when I try to make this field bigger I get the message "Insufficient
disk space". The program is on drive c: and there is 24 GB free disk
space and the files are on drive d: with 20 GB free disk space.

what do I need to do to make the field bigger?
I made the blocksize in BDE enigine bigger to 32000 something but that
doesn't help.
I'm not a IT specialist, so if there is a solution please explane it
like you are talking to a kid

I can ofcourse make a new table with a bigger "problem" field and add
the records from one tabel to the other but that is not a real
solution I think.

p.s. I also cannot add new fields to this table. I'm beginning to
think I cannot make any changes to this tabel anymore
Jacob Bax
jacobbax (AT) xs4all (DOT) nl
http://www.xs4all.nl/~jacobbax/
ICQ: 4271003

On Mon, 06 Feb 2006 23:31:20 +0100, Jacob Bax <jacobbax (AT) xs4all (DOT) nl>
wrote:



I tryed this but even that is not posible, think that the only thing I
can do is adding records

Jacob Bax
jacobbax (AT) xs4all (DOT) nl
http://www.xs4all.nl/~jacobbax/
ICQ: 4271003

On Mon, 06 Feb 2006 23:31:20 +0100, Jacob Bax <jacobbax (AT) xs4all (DOT) nl>
wrote:


Jacob Bax
jacobbax (AT) xs4all (DOT) nl
http://www.xs4all.nl/~jacobbax/
ICQ: 4271003

Jacob Bax wrote:
Take a look here. I just got a new PC and had to run this today to fix
my "insufficient disk space" problem.

http://www.thedbcommunity.com/index....arent=category

jacob

The error you see is caused by the BDE using calls to a Win API functions
that can't handle disk drives larger than 2 GB. Go to www.thedbcommunity.com
and look in the Downloads section. You'll find a download named
Fix_For_Incorrect_Bde_error_.....

Download and unzip it, and read the instruction carefully. The zip file also
contains a form used for verying the fix has been correctly applied. This
form will only work correctly for BDE 5.x. Paradox 8 is using BDE4.x unless
you have upgraded the BDE by yourself. I know how to make the form work
correctly for BDE 4.51 but not for previous BDE versions. IMO, you can
ignore the form.

--
Bertil Isberg - CTECH
Paradox buglist:
online: http://web.comhem.se/~u82608896/

"Jacob Bax" <jacobbax (AT) xs4all (DOT) nl> skrev i meddelandet
news:imifu1hsbmsebats2j83c5t7atitvki1mv (AT) 4ax (DOT) com...

Changing the block size in the bde does not effect the existing table. YOu
have to make a new table and move the records. Also, storing pictures in
the table itself is a bad idea for a number of reasons. The best thing is
to store the file name and an alias or pat to the actual picture files and
use a viewer or graphic field to view them from the actual file. It is not
all that complicated to do and will protect the images, reduce the size of
your table, and keep them from being converted to bitmaps as paradox does
when you add graphics into a table.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and non-profits
since 1982

Jacob,
For your qustion, three remarks:
1)
24 characters is a limit size for a field name,
Have a look at the FAQ section from Mike Irwin:
"FAQ:PdoxWin:Paradox & BDE Limitations:2002.07.18"

2)
If you use long field name, you will probably meet another problem with
path of more than 64 characters
(See the release note with the install CD.)

3)
About the insuffisant disk space, it seems you meet the 4 Gb bug
(see
Fix_For_Incorrect_BDE_Error-If_Free_Disk_Space_Exceeds_4GB.zip on the
thedb community. )

HtH,
Régis





Jacob Bax a écrit :

Bertil,

Jacob mentioned in his email that he set the block size to 32k in the
BDE engine, but did not say whether or not he recreated his table and
copied his data to it. I could be wrong, but don't existing tables
continue using the block size they were originally structured with?
That could be his problem.

Michelle

Bertil Isberg wrote:

Sorry,

Missed Dennis' reply.

You could of couse use up space on the hard drives to point where the free
space is no longer a multiple of 4 and then perform the restructure.

Works for me most of the time without the complication of having to apply
Rick's fix.

Mike

"Jacob Bax" <jacobbax (AT) xs4all (DOT) nl> wrote