Re: more help!

new topic     » goto parent     » topic index » view thread      » older message » newer message

>It certainly would! Even with lots of memory, with a file this large (or
>even a few megs) the speed of loading and saving would be too slow to make
a
>practical program.
>
>There are two ways I can think of to solve the problem:
> 1. Create fixed-length records on disk, then you can do
>     reads and writes of single records (using seek, and
>     perhaps sorted index files)
>  2. Use doubly-linked lists - but this wouldn't be efficient with
>      variable length records, either, come to think of it.
>
>Anybody have a better idea?


Raul (or Luis?), Irv is right. That demo is just that, a demo ;) It tries to
show how easy you can create "records" with euphoria, and save/restore them
easily. You have two choices now:

1.- Use Ralf's EDOM2 to store/retrive your data structure to disk (and
compressed!). I'm not sure, but I think you can retrive "slices" of your
structure (if you can't, Ralf will invent a way... that's for sure!).

2.- Use my DBF engine. It's old, long-time-ago-last-updated.... but works! I
even was sanctified by a fellow euphorian who used these routines for a data
recovery. They use Dbase III+ format, so you can write/read files compatible
with old (and new... Access/Delphi/PowerBuilder...?) programs.

You can find both routines on RDS site... mine is at the archive (the
sarcofagus?) and at http://www27.pair.com/daber/architek)

I'm glad there's another user that's seems to be interested on Euphoria for
developing non-games apps.

Regards,
    Daniel Berstein.

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu