Replies

It’s NFS.

We use the shared folder to post files for several people to work on (read, write, print, save, save-as, whatever). Most of the files are Word (.doc), although we also share an Access database and several Excel files. This PowerPoint (.ppt) file is the first one that presented this problem.

Thanks for the suggestion.

Thank you, Catharine.

I looked at the knowledge base article, and it’s way over my head. I think for now we’ll just have to keep saving the file with a new name, and try very hard to remember to delete the older, unedited versions.

I appreciate your help. I don’t necessarily believe that misery loves company, but I am comforted to know that I’m not the only one who has experienced this problem!

WOO HOO!

It worked! I wouldn’t have thought of your solution in a hundred years. Thanks!

I’m very happy to have a work-around, although I admit that the original problem still has me perplexed. But I promise not to obsess on it.

Originally, I used the keyboard shortcut for paste (Ctrl+V). I just tried it following your directions (Edit>Paste Special>Paste as Visio Project Drawing Object) and the same problem occurred (the left-most part of the left-most objects are cut off).

If I double-click on the object (as though to edit it using Visio while still in Word), the entire thing is visible. But when I click back into Word, the Visio drawing is truncated again.

The other person just used paste, probably from the toolbar.

Thanks for the tip!

I downloaded the program, and it did successfully compact my database. I was then able to compact the database as usual, from the “Tools” menu, without getting the error message. So whatever the problem was, it seems to have gone away.

Thanks again.

If it’s any consolation, if/when you upgrade to Word2000, the bazillion-color options are available for Word table cells.

I know that’s no help, but I thought I’d throw it out there for what it’s worth.

If you’re working on a Mac and you’re using OSX, you can easily save ANY file as a .pdf by choosing “File–Print–Preview–Save As” (be sure to first choose “print” then “preview” as opposed to choosing “print preview”). Saving as a .pdf is a built-in feature of OSX and it’s a piece of cake.

(Hear that, Mr. Gates?)

Edited by gwhitfield on 15-Mar-02 06:59.

Hyperlinks added

Here’s the url of the thread (I think): http://www.wopr.com/cgi-bin/w3t/showthread…488&fpart=1%5B/url%5D

After searching “help” and “FAQ” and emailing loungeadmin, I’ve been unable to figure out how to insert a link in a post. Sorry…

Anyway, the phrase “custom toolbar buttons” occurs in the original post, which may help you locate the thread.

Did I ever mention that the crashing problem is only intermittent?

Joanne,
Go take a look at the thread I mentioned, then contact Ruth for her code (hers were the last posts in the thread). That way, you might be able to keep your custom buttons but avoid having everyone crashing.

I tried this experiment:

I typed a line of text, then underlined the entire line. Using Format/Font/Character Spacing, I set the position of one word in the center of the line to “Raised” by 3 pts. And yes, the underlining for that word remained level with the rest of the underlining, but the word itself was raised above the line.

This isn’t exactly a solution for you, but it might give you an idea as to how to solve your problem.

I recently upgraded to Windows 2000 then Office 2000, and immediately began experiencing Word crashes upon closing documents (see thread “Template Crashes Word (Word97sr2 (win2000))” from January 9, 2002).

The consensus seems to be that there’s a known “issue” involving custom toolbars. Read through the replies to that thread–one kind person even offered some code that would automatically close any toolbars before closing the document or program. I’m not sure if this is the same problem you’re experiencing, but the posts might be useful.

My solution was simply not to use the custom toolbars. My work takes longer, but if my employer really cared about that, I wouldn’t be using Windows and Microsoft products anyway.

Good luck!

David,
I believe the problem is more Access-related than Word-related.

Each row in an Access query or table is the equivalent of a new record, and the command will force each new row to create a new letter. Try setting up a query that will put all of the info for one person into one row. Then each row is a complete record, and your merge should work.

In your database, do you have separate fields for each manual? If so, you wouldn’t have to use . You’d just put in the field names. If the fields are blank in Access, they’ll be blank after the merge (unless you specify otherwise using the conditional statements).

You might try posting this question in the Access forum. Good luck!

To Jen and Hedgehog:

I thought you might be interested in the “resolution” to my problem. I upgraded to Word 2000, after which I totally re-created the template from scratch (not copying ANYTHING). I re-created all of the styles, then re-mapped them to their own toolbar. And yes, documents created with the template still sometimes crash Word upon closing the documents.

Deep sigh.

So my solution is to NOT use the toolbar at all, instead using the more cumbersome method of choosing the style from the toolbar button that’s a drop-down list of styles. Not much of a solution, but I comfort myself by repeating “I get paid by the hour” as my mantra.

Thanks again! Your suggestions were most helpful.

I’m afraid I spoke too soon. The new template just crashed Word on me. Perhaps one of the styles is the corrupt critter. Or maybe there’s something in the header. Or who the hell knows.

I blame Bill Gates.

Anyway, thanks for trying.

I created a brand-new template, then used “Organizer” to move the stypes to the new template, then made new toolbar buttons for easy access to the new styles.

So far , I’ve been able to create and close documents based on the new template, without crashing Word.

Thanks for the idea! It looks like my problem may be solved.