B
B. R. 'BeAr' Ederson
Are you accepting the challenge?
If he did, he should take a different approach than he described above.
With todays typical physical and virtual memory sizes such files should
only be edited 'disk based'. That said: Even if the file has to be
changed in size, parts of it have to be resorted, and so on - one ought
to load a manageable amount of sectors to memory and leave the rest
temporarily untouched. There's a lot of housekeeping needed to do this
in a clean way, though... ;-)
The OP sounded like the file was some sort of csv?
Actually, I don't think so. I rather believe in the ESRI *.e00 exchange
format or similar data. I've only seen such amounts of GIS data apart
from dedicated GIS servers if people blunder with the latest ArcGIS.
:-(
To be more specific: the *.e00 files contain sectionwise fixed length
data streams with entry headers (for instance file names and column
descriptions); all maybe of different wide. And it might be packed,
moreover. Could be a mere mess to deal with. :-(
BeAr