Once I wrote a library which loaded a dataset into memory at new(). Then while the library was used by the mastering script, this data was altered. Then, when the master was done, the library wrote back the modified data via the magic DESTORY() sub - effectively implementing a simple SQL transaction behaviour. -Just as an example... But if this is what DESTROY _should_ do.... Well, it's what it _can_ do.