> You may want to look at the BResources chapter in the Storage Kit > section of the BeBook. In short, a resource is data that is bundled > with an application. Typical examples are the application's icons, > its signature, its launch flags (single launch, multiple launch, > etc), and version information. However, you can associate any kind > of data with your files, such as pictures, sounds, cursors, and > text. Resources are different from attributes because they are > stored inside the files themselves, and are typically used only for > applications. There probably is a very good reason why attributes > aren't used for this, but I can't think of one. Well, resources work also in a non-attribute world and are not as "volatile" as attributes -- i.e. you can't, for instance, lose them accidentially when copying the file, and the end-user usually has no means to edit them (resource editors are strictly developer tools). CU, Ingo