Re: My table turns gray



There's three possibilities that come to mind:

1) Document is corrupt

2) Table is corrupt

3) Computer doesn't have enough memory.

Let's start with number one -- Do a Maggie:

The Maggie:

1. Create a new blank document
2. Carefully select all of the text in the bad document EXCEPT the last
paragraph mark
3. Copy it.
4. Paste in the new document.
5. Save under a new file name and close all, then re-open.

This technique for de-corrupting is known as "Doing a 'Maggie'", after
Margaret Secara from the TECHWR-L mailing list, who first publicised the
technique.


If that doesn't cure it, let's try number 2:

1) Every five pages or so, go click in one of the cells in the Table.

2) Use Table>Split Table to create a break in the table, so Word can catch
its breath when trying to paginate that table.

If that doesn't fix it either, we need to know more about your computer. An
Intel needs at least a gig of RAM to handle large tables, a PPC needs 2GB.

You can get away with less by rebooting to clear the memory, and then
quitting all of the other applications while working on the table. But I
wouldn't bother, if you have only a gig, that's likely to be your problem.

Cheers


On 15/10/08 7:41 AM, in article 59b5ce59.-1@xxxxxxxxxxxxxxxxxxxxxxx,
"mindyjo@xxxxxxxxxxxxxxxx" <mindyjo@xxxxxxxxxxxxxxxx> wrote:

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)

I am typing in a large table. Every few key strokes, my entire file turns
gray, except for a few of the table cells. I have to close the file and
re-open. This is happening more and more often and it is very time consuming
to keep opening & closing the file. Anyone?????

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:john@xxxxxxxxxxx

.



Relevant Pages

  • Re: Out of memory?
    ... 12 GB partition is a nightmare. ... properly allocating enough memory to shrink it then ... >> 2 gigs is not much on a 12 gig drive. ... >> prevents AD from getting so big that this surfaces...but a corrupt AD>> db ...
    (microsoft.public.windows.server.sbs)
  • Re: Vista 64 System needs Extended warm-up
    ... Note that with the total 8 Gig of memory I had the "normal" problem of not being able to install Windows until I had stripped the memory down to only 4 Gigs in the first 2 slots. ... Installation went OK with only 2 sticks of memory, but I needed to do a repair installation a couple of times to remedy a "forever boot" that included a full completion of POST to FF. ...
    (microsoft.public.windows.vista.general)
  • Vista 64 System needs Extended warm-up
    ... Note that with the total 8 Gig of memory I had the "normal" problem of not being able to install Windows until I had stripped the memory down to only 4 Gigs in the first 2 slots. ... Installation went OK with only 2 sticks of memory, but I needed to do a repair installation a couple of times to remedy a "forever boot" that included a full completion of POST to FF. ...
    (microsoft.public.windows.vista.general)
  • Re: Re: Blue screen PFN_list_corrupt
    ... > should display blue screens is if you blue screen while ... > passing bad memory descriptor lists. ... > corrupt The number of pages available 0 The list head was ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Gateway FX6800-01e----Is this computer ok?
    ... Carole Clark wrote: ... The Graphic card you will ... Two of the people told me that yesterday, and today I said I should by more memory and 2 of the techs said that was plenty, like 6G of DDR2. ... A gig is a gig is a gig, ...
    (comp.sys.ibm.pc.games.rpg)

Quantcast