QUESTION/PROBLEM: I registered all of the contestants (about 30) and entry went smoothly. I saved my work before I quit. Now I cannot get MacTD to open the file. I can open it with ClarisWorks...no problem, but when I try to "load MacTD data" I get the following message: "This operation failed because an error occurred: 'Can't understand arguements of "put".' in GlobalMacTDLoad. Please contact the author or publisher of this stack for assistance." Any suggestions? I tried downloading a new copy, but experienced the same problem. I am hoping to begin pairings next weekend, so time is of the essence if I will be able to computerize this worthy children's event. Perhaps there is simply a big gap in my understanding of hypercard. This is my first encounter with it. Could you put me on track, if this is the case? ANSWER: I think the answer to your problem is simple. I'm going to try to guess your problem, but I think I know what it is. I don't think it is a failure to understand HyperCard. I've thrown in a few non-HyperCard tricks (related to the spreadsheet-like windows) that confuse things. Because of the ways these had to be programmed, saving things became slightly non-intuitive. First of all, you should be using at least version 1.01 of MacTD. Version 1.02 is slightly better and is what is currently down-loadable from my web site. Version 1.02 comes with complete documentation for the new version and it is possible that reading this documentation will answer your questions. Nevertheless, I'll try to answer them here. The new documentation makes the old documentation (v0.62) obsolete. I'll put a text version of the documentation on my web site in case the compressed Word documentation is unreadable to you. (also a rich text version to cover all bases...) Every "spread-sheet like" window in MacTD can be saved separately, usually by a menu item. For example, the registration data can be saved when you are at the Registration Card by choosing "Save to File" from the Registration Menu. The database info can be saved (should you choose to make your own database, or import a new one) when you are at the Database Card by choosing "Save to File" from the Database Menu. The info for a particular section can be saved by making sure it is the active section (by going to the Section Manager Card and clicking on it, for example), then going to the Section Micromanagement Card, then choosing "Save Section" from the Section Menu. Etc. When you save components of MacTD in this manner, each component is stored as a comma-delimited table. Such tables should be easy for any Spreadsheet or Database program to import and modify, should you wish to do so for some reason. I suspect this is what you have done with your registration data. I suspect you registered everyone, then chose "Save to File" form the Registration Menu (while you were at the Registration Card). To load this data into MacTD, one would return to the Registration Card and select "Import File" from the Registration Menu. The ability to save components adds a lot of basic flexibility for importing, exporting, and modifying data, as well as for mixing and matching different components. That said, most of the time, it is just easier to save *all* the components at once. To do this, choose "Save MacTD Data" from the File Menu, which should always be available, no matter what Card you are at. "Save MacTD Data" also saves all the options in the Options Card, which doesn't happen with any of the other "Save" menu options. Additionally, it saves information about the state of the Stack, so that when you return, it will be as close to possible as the state it was in before you saved it. "Save MacTD Data" is the bread-and-butter save command that I reccomend using to the exclusion of all other save commands, unless you have a particular reason to save or export or modify externally a component. The file created by "Save MacTD Data" is very difficult for another program to read, so I doubt the file you were able to see in Claris Works was created by "Save MacTD Data." Hope this solves your problem.