Re: Cascading Windows
- From: "Tony Jollans" <My Forename at My Surname dot com>
- Date: Wed, 15 Feb 2006 18:45:24 -0000
Thank you Beth.
It's nice to get a different viewpoint. I think it's easy to use
'corruption' as a reason for something one can't understand - and deleting
normal.dot or registry keys tends to (a) get round many issues and (b) hide
the evidence. And so the myth continues to gain strength.
I'm not entirely sure I agree that 2003 is more stable than earlier releases
but it does handle abends much better so users are less likely to lose work
(which is a big improvement) when they happen.
As I said, I usually put it down to user error when no other explanation is
obvious. I certainly always like to know why (or at least under what
repeatable circumstances) but determining that requires me to remember what
I did yesterday - which isn't always easy :-)
--
Enjoy,
Tony
"Beth Melton" <bmelton@xxxxxxxxxxxxxxxxx> wrote in message
news:OpjNOilMGHA.1028@xxxxxxxxxxxxxxxxxxxxxxx
Hi Tony,
I have a different 'take' on this issue than others. :-)
Changes to the defaults are typically attributed to a third-party
add-in or template. So if you notice your settings have been changed
then that's the first place to start looking. There are a LOT of
add-ins and templates out there that modify Tools/Options along with
various preferences. For example some of the Resume templates created
by Microsoft will turn table gridlines off, field shading, non
printing characters, field codes, etc. Others may turn on the Drawing
Grid, force the view as Print Layout etc.
Nothing can simply 'magically' change nor is Word 2003 more
susceptible to corruption than previous versions. It's a computer
program - it does what it is 'told' to do. Personally, I find it to be
the most stable of all the versions released. I suspect the reason we
encounter this issues more is because of the growing number of add-ins
along with the availability of templates for Word.
Any time I've ever encountered a change in my preferences I've always
found an add-in or template to be the cause. Granted that requires a
little effort to open templates and check the code, or in the case of
an add-in and you can not view the code due to a locked project or a
COM Add-in, it takes a little experimenting to determine the precise
changes that are being made. (But then I'm that oddball who wants to
know WHY. <grin>)
Of course, if you don't care to find the exact cause then force the
settings you want using a macro. But at the very least, know it is a
third-party and not caused by instability. :-)
Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
"Tony Jollans" <My Forename at My Surname dot com> wrote in message
news:Obb7BY7LGHA.3896@xxxxxxxxxxxxxxxxxxxxxxx
Graham,
I've been suspicious for some time that Word 2003 changes settings
all by
itself but I usually put it down to user error as I routinely change
all
manner of my own settings (just to see the effect).
Is there anything known about this? Are any particular settings more
susceptible than others? Does any particular type of action, or
document,
tend to cause it?
--
Enjoy,
Tony
"Graham Mayor" <gmayor@xxxxxxxx> wrote in message
news:eirw3r6LGHA.2580@xxxxxxxxxxxxxxxxxxxxxxx
Tony has identified the likely cause, but as this may happen again
(Word
2003 can do that), it would be worth adding the line
Application.ShowWindowsInTaskbar = True
to your macro to ensure it is correct each time you run it.
--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP
My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Joanne wrote:
System: Dell Opti Flex, 1gb memory, winxp pro, MSoffice 2003
I use a macro called 'get files' to open 50 text files at a
time -
here is the code for the macro, to which I have made no changes:
Public Sub GetFiles()
'Application.CommandBars("Main Menu").Visible = False
Dim Resumes As String, FileArray() As String, Num As Long,
OpnFile As
Long
Dim PassNum As Integer, temp As String 'sorting variables
Dim Upper As Long 'Upper boundary of array
ReDim FileArray(150)
Num = 0 'Setting counter to 0
OpnFile = 0 'Setting counter to 0
Resumes = Dir$("C:\1\ceweekly\*.*") 'Where the files are at
Do While Len(Resumes) > 0 ' Loop to put files into an array
FileArray(Num) = Resumes
Num = Num + 1
Resumes = Dir$
Loop
ReDim Preserve FileArray(Num - 1)
Upper = UBound(FileArray)
' Sort array
WordBasic.SortArray FileArray
' Open the files for editing
For OpnFile = 0 To 49
If OpnFile <= Upper Then 'if there are files in the array
Documents.Open FileName:="C:\1\ceweekly\" _
& FileArray(OpnFile) 'then open the next one and increment
counter
ActiveWindow.ActivePane.View.Zoom.Percentage = 118
End If
If OpnFile = -1 Then
Application.Quit
End If
Next
End Sub
Until today, the files would open on top of each other on the
screen
and in a 'group' in the taskbar. Now all of a sudden the files
are
opening in 'cascading windows' which causes me to do a lot of
extra
clicking and window moving so that the files are not on top of my
other 2 apps that I am running to process the files. I want them
to
open in msword 2003 (which is living only on the top 50% of my
screen
and allowing me to use the bottom 50% for the other 2 apps). I
don't
remember making any changes anywhere and so I can't figure out
how to
get this to work as it was before today, MSWord owns top of
screen,
other apps own bottom of screen and all files open on top of each
other with no cascading down the screen. Can someone please help
me
get this fixed? I tried using the ApplicationWindowState and
chose
'minimize', but then I have to click them one at a time to get
them on
the screen again and they come back in their cascaded position,
leaving me with my other apps behind them again. Don't know what
else
to try.
Thanks for your time and help
Joanne
.
- Follow-Ups:
- Re: Cascading Windows
- From: Suzanne S. Barnhill
- Re: Cascading Windows
- References:
- Cascading Windows
- From: Joanne
- Re: Cascading Windows
- From: Graham Mayor
- Re: Cascading Windows
- From: Tony Jollans
- Re: Cascading Windows
- From: Beth Melton
- Cascading Windows
- Prev by Date: Re: Cascading Windows
- Next by Date: Re: Locking Toolbars
- Previous by thread: Re: Cascading Windows
- Next by thread: Re: Cascading Windows
- Index(es):