>Hi Hilmar,
>
>Well, my purpose is to an object in a way so that i can restore it with all its functionality as fast as possible. You tell me that the file-size can increase very quickly and that means slowing down the retrieval of the object i think. Therefore it looks like i have to follow your suggestion but it will require more programming.
>My thoughts were, if i can store an entire object and retrieve it the same way i don't have to worry about reading and writing every property. You showed a way to do this in an easy way and is for me a good solution.
>But i am still curious if an object can be stored and retrieved in a general field. If it can be done, i can compare the performence of both methods to see which method delivers the best way to do it.
>
>Thanks for your helpful advice,
>
>Erwin
Take a look at APPEND GENERAL, as I already suggested.
Speed isn't the only issue, I think. Size may be an issue, too, if it becomes ridiculously large. For instance, to store JPG-files, we need ca. 50 KB (as JPG-files). Importing the selfsame files into general fields takes >1e6 bytes per image (a factor of 20). For storing over 1000 files, the disk space becomes significant (just imagine the additional trouble of doing backups!).
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)