>This is my biggest criticism now. I really WISH it could be fixed. >Unfortunately, the notes would have to accept tabs. I would be very unhappy with tabs as the solution. I think the only good solution would be a way to specify that portions of notes were to be rendered in a monospaced font. Then, your spacing would be maintained. (Cf. the <TT> tag in HTML. The <TT> tag does not necessarily specify that a particular monospaced font such as Courier is to be used, but it does specify that *some* monospaced font is to be used.) In my view, the problem with tabs is that there is absolutely no standard in the computing industry as to how they are to be rendered. Let me give three examples of the problem. 1. Several years ago, I participated in an E-mail discussion list about the mathematics of Rubik's cube. Several of the subscribers would routinely post messages (usually tabular in format, giving results of some of their research) which used tabs heavily. If you were using a UNIX based non-graphical E-mail system, then the messages looked fine because such systems "expanded" the tabs in the manner in which the person who posted the E-mail expected. If you were using any other E-mail system (including nearly all modern E-mail systems, for example), then the messages were so wavy they were almost impossible to read. 2. Closer to home, the ASCII reports produced by Family Origins make heavy use of tabs. If I cut and paste from these reports into an E-mail I am composing, then the E-mail becomes wavy and hard to read. Worse yet, the degree of waviness and the difficulty of reading depends totally on which E-mail client my correspondent is using. And often, my "correspondent" is an E-mail discussion list, so there are a wide variety of E-mail clients in use by people who are reading my message. I don't know how to make a report that can be read by everybody because of the tabs. Therefore, high on my wish list for V11 (I also posted it for V10, both here and on the official wish list page) is a way to produce ASCII reports without tabs, in a monospace font, and with few enough characters per line that they can be posted via E-mail without distortion. The RFT files produced by Family Origins are great, but they are not a solution for my tabs problem. I can send them as attachments to individual correspondents, but I cannot send them to Rootsweb lists because Rootsweb does not allow attachments. As long as reports stay as RTF files, the tab problem vanishes. Any word processor you load them into handles the tabs just fine. But if I cut and paste them into E-mail, it's the same problem as with ASCII reports. 3. I have the complete (nationwide) set of 1880 census CD's produced by the LDS. You can cut and paste a census entry from their screens into an E-mail, into a note in Family Origins, or into whatever. But the text which has been cut and pasted is full of tabs, and after cutting and pasting is generally rendered in such as way as to be very difficult to read. You can edit the text to delete the tabs and replace them with spaces to make the text readable. But I find the process so clumsy and labor intensive that it's easier and faster just to retype the text that I would prefer to cut and paste. So I say no to tabs. A thousand times no. Please. Jerry Bryan _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp