Anthony :) jobcontrol, I realize that the .obj file as intermediate compiler-linkage object has been around for a long time. It's just that there are many extensions that are used to mean various things, and collisions occur more frequently than noted. But the extension should not be considered the end all of filetype. I come from an Amiga background, where file extension meant diddly. The same goes for many *nix systems. I believe that the same goes for MacOS (but am not certain). Actions about how the files were handled was totally dependent upon the content, especially binary files. If the format was plain text, but had no specific handler, it would open in a text editor-browser. But if it had information that, for instance, singled it out as an A|W 3D object exchange format, it could be set to take the appropriate action. This poor gentleman in Hong Kong obviously has no conception of this. It's a .obj and he's a programmer, then it must be a compiler object. Wrong! If I were to rename every file on my system .obj, under Windows, it is quite clear that Windows would never boot again (and that not all of the files are A|W 3D objects or compiler objects). That's not my fault, that's M$'s fault for using a flawed system of file type determination. Not certain how long .obj has been used as a 3D object, but it has been around for at least a decade, maybe two. BYS