Access Causes Permanent Problem in MSWord

[Gus]

We create reports in MSWord 2000 from within our Access 2002
application. The report template uses a lot of tables and nested
tables.

Over time, many hundreds of reports, Word has become difficult to use in
a way that looks like a memory/display problem.

In simple terms, the screen does not update when I change things in the
document ie delete a line. Table borders do not display on the screen.

These problems affect all Word documents on my machine but do not affect
any word documents on other machines.

It looks like there is some stuff being left lying around but I don't
even know how to think about this. I haven't even seen anything
remotely like this described anywhere.

Does anyone have a clue.

*** Sent via Developersdex http://www.developersdex.com ***

[Terry Kreft]

Sounds more like a video driver problem to me.

--

Terry Kreft
"Gus" <gu*********@hotmail.com> wrote in message
news:Au***************@news.uswest.net...

We create reports in MSWord 2000 from within our Access 2002
application. The report template uses a lot of tables and nested
tables.

Over time, many hundreds of reports, Word has become difficult to use in
a way that looks like a memory/display problem.

In simple terms, the screen does not update when I change things in the
document ie delete a line. Table borders do not display on the screen.

These problems affect all Word documents on my machine but do not affect
any word documents on other machines.

It looks like there is some stuff being left lying around but I don't
even know how to think about this. I haven't even seen anything
remotely like this described anywhere.

Does anyone have a clue.

*** Sent via Developersdex http://www.developersdex.com ***

[Jan]

Have you checked to be sure you're releasing Word at the end of the
Access module? Otherwise you may be creating multiple instances of Word
and they could accumulate after a while. Some clues: when you open
Word, does it go to Document1 as the default blank, or is it a higher
number? Also, you could look in the Task Manager Processes tab and see
how many instances of WinWord.exe are running.

Good luck.

Jan

Gus wrote:

We create reports in MSWord 2000 from within our Access 2002
application. The report template uses a lot of tables and nested
tables.

Over time, many hundreds of reports, Word has become difficult to use
in a way that looks like a memory/display problem.

In simple terms, the screen does not update when I change things in
the document ie delete a line. Table borders do not display on the
screen.

These problems affect all Word documents on my machine but do not
affect any word documents on other machines.

It looks like there is some stuff being left lying around but I don't
even know how to think about this. I haven't even seen anything
remotely like this described anywhere.

Does anyone have a clue.

*** Sent via Developersdex http://www.developersdex.com ***

[pietlinden]

>

Does anyone have a clue.

Not much of one, but posting your code would help a lot.

[Anne Nolan]

Could be a messed-up NORMAL.DOT file, too.

Anne
"Gus" <gu*********@hotmail.com> wrote in message
news:Au***************@news.uswest.net...

We create reports in MSWord 2000 from within our Access 2002
application. The report template uses a lot of tables and nested
tables.

Over time, many hundreds of reports, Word has become difficult to use in
a way that looks like a memory/display problem.

In simple terms, the screen does not update when I change things in the
document ie delete a line. Table borders do not display on the screen.

These problems affect all Word documents on my machine but do not affect
any word documents on other machines.

It looks like there is some stuff being left lying around but I don't
even know how to think about this. I haven't even seen anything
remotely like this described anywhere.

Does anyone have a clue.

*** Sent via Developersdex http://www.developersdex.com ***