Cannot activate "Track Changes" on Word 2004 for Mac

T

Tony

John,

Thanks for the comprehensive reply.

Actually, I did as you suggest. In fact, the "corrupt" Word (.doc) file
arrived with all three "Tools/Track Changes/Highlight Changes" options
unchecked. Accepting all changes and saving it with a different name
did not help. At least with that particular file.

I will do as you indicate in the other topics.

How to copy/save multiple items in Word? Can it be done with any Office
application for Mac? With any other application on the Mac?

Concerning the paste plain text, I could finally make a macro and
keyboard shortcut (see above). But as far as I understand, that is
based in Visual Basic, which will not be available on Office 2008 for
Mac. Check out:

Microsoft makes a Basic mistake with Office 2007 - Dropping support for
Visual Basic scripting makes Office suite DOA

http://www.macworld.com/2006/12/opinion/microsoft/index.php

Thanks again.

---
 
J

John McGhie

Hi Tony:

You never sleep?? :)

The Office Clipboard: Have a look in the Help and see if you can find it.
I think it will refer you to this:
http://www.microsoft.com/mac/produc.../mac/library/quick_solutions/of_Scrapbook.xml

Sorry: My ex-Mac is in LA and I am in Sydney right now, so it's a little
difficult to look it up. I need to get a new Mac, but that hasn't happened
yet.

The paste macro you are using is not my favourite one: it has a weakness in
that if the content of the Clipboard "cannot" be pasted as text, it will
blow up. This is the one I use, which does an ordinary paste if the thing
on the clipboard is not "text".

Sub PasteUnformatted()
On Error GoTo notAvailable

Selection.PasteSpecial Link:=False, DataType:=wdPasteText
End

notAvailable:
Selection.Paste

End Sub

And you are quite correct, that is indeed VBA. Very observant of you :)

You are quite correct: Office 2008 will have no VBA.

These two facts are unrelated to what I said before. :)

Cheers
--

John McGhie, Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs

+61 4 1209 1410, <mailto:[email protected]> mailto:[email protected]
 
C

CyberTaz

Hi Kids -


On 4/7/07 6:34 AM, in article (e-mail address removed), "John

The Office Clipboard: Have a look in the Help and see if you can find it.
I think it will refer you to this:
http://www.microsoft.com/mac/products/office2004/using.aspx?pid=usingoffice200
4&type=howto&article=/mac/library/quick_solutions/of_Scrapbook.xml

Correct, as usual :), but it's only fair to clarify that the Mac Office
Scrapbook is not at all the same as the PC Office Clipboard... The former
being a stored repository of items retained after quitting or shutting down,
whereas the latter is a volatile multi-item "clipboard" the content of which
is cleared when all office apps are quit. I believe the PC Office Clipboard
(in 2003) is limited to 24 items.
Sorry: My ex-Mac is in LA and I am in Sydney right now, so it's a little
difficult to look it up. I need to get a new Mac, but that hasn't happened
yet.

You must be on the verge of withdrawal by now;)
The paste macro you are using is not my favourite one: it has a weakness in
that if the content of the Clipboard "cannot" be pasted as text, it will
blow up. This is the one I use, which does an ordinary paste if the thing
on the clipboard is not "text".

Which is exactly why I prefer it - not being overly proficient with VBA the
runtime error lets me know if I've inadvertently copied something I
"thought" was text & actually turns out to be something else. The rte better
serves my preferences than your error trapping - but I fully appreciate your
point. The "something else" doesn't get pasted as you mention, but as soon
as I OK the error I can still do a regular Paste or Paste Special. Also, If
I've copied something - such as a table - which includes both text &
graphics the text *does* get pasted plain, but the graphics are omitted
(without the rte occurring.). OTOH, if I've *knowingly* copied mixed content
or graphics and *want* to paste all I've copied I use a standard paste
command, I *don't* paste using the macro.
<snip>

Regards |:>)
Bob Jones
[MVP] Office:Mac
 
J

John McGhie

The school I attended told me it was very poor practice to sell users
programs you knew were going to blow up :) It could get end users into
trouble because they may not have access rights to the VBA Editor, in which
case the error would hang the application and leave them to lose data.

Just in case *anyone* is in the slightest bit interested, Word makes it
impossible to do the right thing and enquire beforehand to see what is
actually IN the clipboard. It's one of the things they forgot to implement
in VBA.

That's the only macro I run that intentionally relies on the "On Error GoTo"
statement, which is otherwise the sort of programming pactice for which
death should be slow and agonising.

If you are working in C++ or C#, you can hook a Windows .dll that will tell
you exactly what's in the clipboard, and which of the many data types or
file formats you can retrieve it in. Not on the Mac, of course. Maybe in
AppleScript...

In the case of Word, the clipboard normally does not contain physical data,
it contains a "pointer" to the source. So if Word put the item on the
clipboard, you can retrieve it in any of the formats for which Word has an
export filter.

I did have another version of the macro that would walk down a SELECT
statement trying each format in turn to see which one would paste without
error. But that can give unpredictable results :) So I settled on the
simpler version, which attempts a paste as Text, then gives up and lets Word
figure it out if that won't do. This suits me, because I use that Macro as
my standard "Paste" command: I rename the macro "Sub EditPaste()" which
causes the macro to replace the built-in Word command everywhere.

Cheers

--

John McGhie, Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs

+61 4 1209 1410, <mailto:[email protected]> mailto:[email protected]
 
T

Tony

Hopefully, Word 2008 (and PowerPoint 2008) will have a keyboard command
to paste unformatted text. My favorite is the standard:

Command V
 
J

JE McGimpsey

The paste macro you are using is not my favourite one: it has a weakness in
that if the content of the Clipboard "cannot" be pasted as text, it will
blow up. This is the one I use, which does an ordinary paste if the thing
on the clipboard is not "text".

Which is exactly why I prefer it - not being overly proficient with VBA the
runtime error lets me know if I've inadvertently copied something I
"thought" was text & actually turns out to be something else. The rte better
serves my preferences than your error trapping - but I fully appreciate your
point.[/QUOTE]

I'd suggest a different approach for most folks, then. Certainly a
polite message would be more friendly and more meaningful than a RTE,
and some people won't have access to the debugger (or know what it is):

Public Sub PasteUnformatted()
Dim errResult As Long
On Error GoTo ErrHandler

Selection.PasteSpecial _
Link:=False, _
DataType:=wdPasteText
ResumeHere:
Exit Sub
ErrHandler:
errResult = MsgBox(Prompt:= _
"Unable to paste unformatted text into Selection" & _
vbNewLine & "Cancel to resume, OK to enter debugger", _
Title:="PasteUnformatted", _
Buttons:=vbOKCancel + vbDefaultButton2)
If errResult = vbCancel Then
Resume ResumeHere
Else
Stop
End If
End Sub


Perhaps the error handling could be broken out further...
 
D

Daiya Mitchell

Clive said:
On 7/4/07 1:41 AM, in article (e-mail address removed), "Daiya



I mentioned the iClip problems on 22 Sep 05, 28 Oct 06 and 18 Jan 07. ;-)

shame on me..... :) I didn't look, just trusted my memory.

Daiya
 
C

CyberTaz

Hi John & John -

I suppose I should clarify the previous by adding:

1- I *don't* recommend the RTE route for end-user distribution - I simply
meant that it serves my personal requirements. I merely offered it up as a
thought-provoking alternative (which seems to have served its purpose quite
well;-}). McGimpsey's code is certainly more elegant, but - alas - that is a
talent which I fear I have not developed :( Rest assured, however, that I
have already taken full advantage of his generosity:) Thanks, John.

2- The debugger issue isn't an issue if you don't click the Debug button. I
just click the End button instead.

Regards |:>)
Bob Jones
[MVP] Office:Mac



Which is exactly why I prefer it - not being overly proficient with VBA the
runtime error lets me know if I've inadvertently copied something I
"thought" was text & actually turns out to be something else. The rte better
serves my preferences than your error trapping - but I fully appreciate your
point.

I'd suggest a different approach for most folks, then. Certainly a
polite message would be more friendly and more meaningful than a RTE,
and some people won't have access to the debugger (or know what it is):

Public Sub PasteUnformatted()
Dim errResult As Long
On Error GoTo ErrHandler

Selection.PasteSpecial _
Link:=False, _
DataType:=wdPasteText
ResumeHere:
Exit Sub
ErrHandler:
errResult = MsgBox(Prompt:= _
"Unable to paste unformatted text into Selection" & _
vbNewLine & "Cancel to resume, OK to enter debugger", _
Title:="PasteUnformatted", _
Buttons:=vbOKCancel + vbDefaultButton2)
If errResult = vbCancel Then
Resume ResumeHere
Else
Stop
End If
End Sub


Perhaps the error handling could be broken out further...[/QUOTE]
 
D

Daiya Mitchell

I think so. I've messed with my menus. But basically, bring up the
dialog that lists all the macros, select the one and hit Run. That makes
sure the macro works. Most efficient to test it before you even bother
creating the keyboard shortcut.

Glad you solved it.
 
J

JE McGimpsey

CyberTaz said:
2- The debugger issue isn't an issue if you don't click the Debug button. I
just click the End button instead.

You're absolutely right. The issue my suggestion addresses is the
unhelpful Error dialog.
 
P

Phillip Jones

They are just endorsing the "shotgun approach" if this don't work try
this, :-D

Daiya said:
Could y'all decide what edits need to be made to this page?
http://word.mvps.org/Mac/PasteText.html

Cause the inefficiency of seeing multiple solutions proposed every time
is starting to grate on me. :)
Daiya

--
------------------------------------------------------------------------
Phillip M. Jones, CET |LIFE MEMBER: VPEA ETA-I, NESDA, ISCET, Sterling
616 Liberty Street |Who's Who. PHONE:276-632-5045, FAX:276-632-0868
Martinsville Va 24112 |[email protected], ICQ11269732, AIM pjonescet
------------------------------------------------------------------------

If it's "fixed", don't "break it"!

mailto:p[email protected]

<http://www.kimbanet.com/~pjones/default.htm>
<http://www.kimbanet.com/~pjones/90th_Birthday/index.htm>
<http://www.kimbanet.com/~pjones/Fulcher/default.html>
<http://www.kimbanet.com/~pjones/Harris/default.htm>
<http://www.kimbanet.com/~pjones/Jones/default.htm>

<http://www.vpea.org>
 
J

JE McGimpsey

Daiya Mitchell said:
Could y'all decide what edits need to be made to this page?
http://word.mvps.org/Mac/PasteText.html

Cause the inefficiency of seeing multiple solutions proposed every time
is starting to grate on me. :)

Well, you could put this in (which is a modification of my paste
unformatted text sub), but I suspect some others may object to it as
overkill:

Public Sub PasteUnformattedText()
'If Word cannot paste unformatted text, then setting
'the constant cbDebugMode to False in the line
'below will cause Word to automatically attempt to
'paste whatever is on the clipboard. Setting
'cbDebugMode to True will give the user the opportunity
'to enter the debugger.
Const cbDebugMode As Boolean = True

'If Word should give warn the user that the attempt to
'paste failed, and give them an option to abort, then
'set cbWarnMode to True. If Word should paste the
'clipboard contents without a warning, set cbWarnMode
'to false.
Const cbWarnMode As Boolean = True

Const csProcedureName As String = "PasteUnformattedText"
Const csMsg1 As String = "Unable to paste unformatted " & _
"text into Selection." & vbNewLine & vbNewLine

Const csMsg2 As String = "Click Yes to paste clipboard " & _
"contents, No to enter debugger, or Cancel to abort pasting."

Const csMsg3 As String = "Click OK to paste clipboard " & _
"contents, or Cancel to abort pasting."

Const csMsg4 As String = "Unable to paste from the " & _
"clipboard into Selection." & vbNewLine & vbNewLine

Const csMsg5 As String = "Click OK to enter debugger, " & _
"or Cancel to abort pasting"
Dim nErrorResult As Long

On Error GoTo ErrorHandler
Selection.PasteSpecial _
Link:=False, _
DataType:=wdPasteText
ResumeHere:
Exit Sub
ErrorHandler:
On Error Resume Next 'no errors in error handler

'If in debug mode, allow user to choose debug.
If cbDebugMode Then
nErrorResult = MsgBox( _
Prompt:=csMsg1 & csMsg2, _
Title:=csProcedureName, _
Buttons:=vbYesNoCancel + vbDefaultButton2)
If nErrorResult = vbNo Then
Stop
Resume
ElseIf nErrorResult = vbCancel Then
Resume ResumeHere
End If
ElseIf cbWarnMode Then
nErrorResult = MsgBox( _
Prompt:=csMsg1 & csMsg3, _
Title:=csProcedureName, _
Buttons:=vbOKCancel + vbDefaultButton2)
If nErrorResult = vbCancel Then Resume ResumeHere
End If
Err.Clear
Selection.Paste
If Err.Number <> 0 Then
If cbDebugMode Then
nErrorResult = MsgBox( _
Prompt:=csMsg4 & csMsg5, _
Title:=csProcedureName, _
Buttons:=vbOKCancel + vbDefaultButton2)
If nErrorResult = vbOK Then
Stop
Resume
End If
ElseIf cbWarnMode Then
MsgBox _
Prompt:=csMsg4, _
Title:=csProcedureName, _
Buttons:=vbOKOnly
End If
End If
Resume ResumeHere
End Sub
 
T

Tony

Thanks!

---

I think so. I've messed with my menus. But basically, bring up the
dialog that lists all the macros, select the one and hit Run. That
makes sure the macro works. Most efficient to test it before you even
bother creating the keyboard shortcut.
Glad you solved it.
 
J

John McGhie

Hi Tony:

Please allow me to commend to you the philosophy embodied in Clive's "Bend
Word to Your Will" :)

I strongly suggest that you don't rely on Microsoft to provide an
application set up to your (or my...) personal foibles: but you can rely on
Microsoft to ensure that you can customise Word precisely to your taste. A
few hours learning how to quickly customise the application, and to preserve
those customisations, will reward you a hundred-fold.

With a bit of luck, all existing predefined keystrokes will be retained in
Office 2008. However, this is made much more difficult on the Mac than it
is in Windows, because the Mac's history of having a single-button mouse
means it's very keystroke-centric. The Operating System keeps "stealing"
keystrokes that users could otherwise assign to their own purposes :)

Keystrokes will not be a big focus for Microsoft: the new Microsoft Office
Fluent User Interface is designed to be used without them. But the ability
to assign them for yourself will remain, and I encourage you to use that :)

I also encourage you to avail yourself of a scroll-wheel mouse, if you
haven't already done so. A five-button mouse will make Microsoft Office
very MUCH faster to use for serious work: Microsoft Office is VERY
right-click-centric. There are those with the view that they are much
faster using Word because they learn and use keystrokes only -- some who
dismiss all the toolbars in the current aplication and drive only with
keystrokes. I applaud their commitment to their convictions :) I would
cheerfully take them on in any contest of productivity, and I think I would
win -- probably nearly double. In the new Office user interface, that
margin can be ten or a hundred times (literally!).

I suppose it's also worth while passing on my current experience of the new
user interface: It is dramatically different from the old one. Almost
every method that I use has had to be changed in some way. I implore people
NOT to try to "make it work the way it always used to." You will get into a
gruesome and extended wrestling match. And ultimately, Word will win. The
only variable is how many hours/days/weeks you are prepared to devote to the
struggle :)

Why not allow the time I have wasted doing this, to suffice for you too?

Approach the problem with one thought in mind "This one is different. I
need to change the way I do everything." I was humiliated to discover that
the less people know about how to use Word now, the faster they pick up the
new user interface :) That, of course, was Microsoft's major design goal,
and they achieved it in spades... {Sob!}

If you hold that thought in mind, within a couple of weeks you will find
that everything you want to achieve is getting done between two and ten
times faster, with less effort, and far higher reliability.

This one is different. It is dramatically more efficient. It is also
considerably more flexible. However, there are some old methods and
techniques that may have to go (depending on how you normally work).

Will all my old documents work? Yes.

Will all my old templates work? Yes.

Will all my old macros work? No. None of them will work.

What about my old toolbars? They will work, but you will almost imediately
abandon them, because toolbars do not make things "easier" in an application
taht is designed to operate without them.

It's going to be a fun time: but the result will be faster, more reliable
and more robust documents.

Hope this helps

How many of my old macros will I actually need? Almost "Zero". Most of my
macros were built to provide functions Word did not have built-in, or did
not do easily. The need for almost all of those will go away :)

--

John McGhie, Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs

+61 4 1209 1410, <mailto:[email protected]> mailto:[email protected]
 
J

John McGhie

Hi Bob:

Oh, sure, I know it works for you, because sometimes I run with a cut-down
version myself that does precisely that :)

This is a macro I use so pervasivlely that if I find yself using a copy of
Word that doesn't have it, I record one immediately that does the trick: but
it doesn't have the bells and whistles.

My comments were only in the pathetic hope that we still had an audience
left following along: I wanted to make sure that we left non-coders with a
lump of code that was properly house-trained :)

Cheers

--

John McGhie, Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs

+61 4 1209 1410, <mailto:[email protected]> mailto:[email protected]
 
C

Clive Huggan

shame on me..... :) I didn't look, just trusted my memory.

Daiya

With *my* memory I can't afford the luxury of relying on it. :)

Which is essentially why I wrote "Bend Word to Your Will".

Which is why I'm here... :-|

Clive
======
 
J

John McGhie

Hi John:

Congratualtions: that macro certainly covers all of the possibilities and
provides USEFUL prompts for the user :)

However, if we're proposing to put that code into Daiya's article, should we
try to tweak the coding style a little closer to what we would recommend
that "others" do? :)

Forgive my failing memory, but I thought "On Error Resume Next" had global
scope within a module? So wherever you put it, it's going to have effect
within the module? I thought you couldn't change it within an error
handler...

Should we be writing modules that "Exit" from the middle of the code.? Or
using a function named "Resume" that in fact "Exits"? :)

I know it works: but is it "extensible, maintainable, and
self-documenting"?? :)

Cheers

--

John McGhie, Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs

+61 4 1209 1410, <mailto:[email protected]> mailto:[email protected]
 
C

Clive Huggan

Tony,

Throughout Mac applications, Command-v pastes what was copied, i.e. =
Formatted.

Pasting unformatted needs a different keyboard shortcut. Maybe, for example,
Command-Option-v. (I chose Command-Option-p for Paste Unformatted, for
reasons that I no longer remember; not sure of whether Command-Option-v was
taken.)

Cheers,

Clive Huggan
============
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top