CompuServe Messages

Herb I did make the macro capable of being run alone, in an open document, although I had hoped no one would try it as the standalone capabilities are not as complete as I'd like them to be (well, they're not as good as the WordPerfect version due to limitations in WordBasic). That said, here's what to do and what happens: Copy DTSWWDDE (Macro), dtswwddeico (AutoText) and all Styles beginning with DTS (i.e., DTSDate) to Normal.Dot. When you run the macro, the macro starts placing its data at the very end of whatever text is in the document. So if there is just a single line or three pages of text in your document, the macro places its data after it. (If your existing documents have headers and date text or fields, you should turn off the Include Header and Include Date Text options in the macro's "Defaults" dialog box.) This is how it's supposed to work, and how it should work. To be honest I haven't done a lot of testing with it as a standalone, but it was certainly my intention that it should work in this way. The only suggestion I would make is to add two Enters after whatever text is in your document, so that the spacing is correct and paragraph styles are not interferred with, etc. The specific DDE code that has to be available in BOOK.EXE is BringOnTop(), which was only added in the August/September '93 releases. I erred on the side of caution with the date I gave in the help file, but I'm glad it works for you, whatever the date of your BOOK.EXE! Also, thank you for the kind words about the macro. The new version, due out next month, is a great improvement over the current version, and should be better able to handle being run as a standalone, although as I say, the current version isn't bad in this regard. Hope this helps. David P.S. BTW, the template can be copied and renamed any number of times, so you can create default templates to your own design, and AutoRun the macro when a new document is based on any one of the templates. The next version of the template/macro will have a dummy template that exists only to run the macro which will probably be stored in Normal.Dot; this is obviously better as the macro only exists in one place on disk.