|
Home > Archive > Programming with dBASE > March 2006 > Updateset - Database Engine Error: Read Failure
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Updateset - Database Engine Error: Read Failure
|
|
| Trevor 2006-03-21, 3:25 am |
| Hi All
I am trying to use updateset to append 6480 records to a table. The
append gets to around 1200 records (this varies) then gives the error:
Database Engine Error: Read Failure
It stops on the last line of the following code.
u = new UpdateSet()
u.source = form.clm_btimp1.rowset
u.destination = ":vt_claims:claims.dbf"
u.append()
Any ideas?
Thanks
Trevor
| |
| Mervyn Bick 2006-03-21, 3:25 am |
| On Mon, 20 Mar 2006 12:39:49 +0200, Trevor < trannnospam@nospammp
x.xom.au>
wrote:
> Hi All
> I am trying to use updateset to append 6480 records to a table. The
> append gets to around 1200 records (this varies) then gives the error:
>
> Database Engine Error: Read Failure
>
> It stops on the last line of the following code.
>
> u = new UpdateSet()
> u.source = form.clm_btimp1.rowset
> u.destination = ":vt_claims:claims.dbf"
> u.append()
I had exactly the same message when I tried to add three fields to an
existing table a few months ago. I never did get an answer to just what
was going wrong but it appears that the trouble in my case was caused by
the fact that there were many large character fields that were indexed on
left(<field>,100). The workaround was to use the table without the
indexes, add the three fields and then rebuild the indexes.
Mervyn.
| |
| Les Shewchuk 2006-03-21, 3:25 am |
| Hit this problem as well.
What is the physical size of the .dbf file you are working with. While
technically the file can be up to 2Gb, I run into this whenever I do any
bulk processing to a table where the size when finished is over 150Mb. (By
bulk, I mean; Pack, Reindex, Append From, Copy To or restructuring a table.
Anything that results in the moving of large amounts of data at one time)
YET, if you are adding only one record at a time to the file, it works no
problem. After all, the file managed to get to be over 150Mb somehow.
This appears to be A BDE problem with dBase tables (I haven't tried it with
Paradox or a Client/Server) It happens to files stored locally or on a
network connection.
Les Shewchuk
"Mervyn Bick" <invalid@invalid.invalid> wrote in message
news:op. s6pvu8sn380wm4@mervy
n1...
> On Mon, 20 Mar 2006 12:39:49 +0200, Trevor < trannnospam@nospammp
x.xom.au>
> wrote:
>
>
> I had exactly the same message when I tried to add three fields to an
> existing table a few months ago. I never did get an answer to just what
> was going wrong but it appears that the trouble in my case was caused by
> the fact that there were many large character fields that were indexed on
> left(<field>,100). The workaround was to use the table without the
> indexes, add the three fields and then rebuild the indexes.
>
> Mervyn.
| |
| Trevor 2006-03-21, 3:25 am |
| Pack / reindex seems to have done the trick.
| |
| Mervyn Bick 2006-03-21, 11:24 am |
| On Mon, 20 Mar 2006 19:42:25 +0200, Les Shewchuk <les@tritonmarine.com>
wrote:
> Hit this problem as well.
>
> What is the physical size of the .dbf file you are working with. While
> technically the file can be up to 2Gb, I run into this whenever I do any
> bulk processing to a table where the size when finished is over 150Mb.
> (By
> bulk, I mean; Pack, Reindex, Append From, Copy To or restructuring a
> table.
> Anything that results in the moving of large amounts of data at one time)
>
> YET, if you are adding only one record at a time to the file, it works no
> problem. After all, the file managed to get to be over 150Mb somehow.
The table I was working with had just under 5000 records with a record
size of 1639 bytes and was about 8Mb in size. There were 2 numeric
fields, 16 character fields and 7 memo fields. The table was indexed on
the two numeric fields and 11 of the character fields.
I needed to edit three of the fields so I was trying to add three 1
character fields to hold markers indicating where changes had been made.
Simply modifying the structure brought up the Read Error message so I had
to get there via the scenic route. <g>
Mervyn.
|
|
|
|
|