| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2915.1 | | NAC::BULEAN::BANKS | Goose Cooker | Wed Apr 30 1997 12:41 | 7 |
| Could it be a word macro virus that didn't survive the change from Word
Basic to VBA? As far as I know, saving a file should not normally
invoke any Visual Basic code, unless some application (or virus) has
been installed.
Check your macros for the presence of an autoexec, autoload or autosave
macro.
|
| 2915.2 | | QUARK::LIONEL | Free advice is worth every cent | Wed Apr 30 1997 20:01 | 5 |
| The "upgrade from wfw 3.11" is the key. You've got macros that invoke 16-bit
DLLs, and this doesn't work with Word 97 (nor Word 95). Remove all the macro
definitions from your template.
Steve
|
| 2915.3 | That worked | CUJO::PADILLA | | Thu May 01 1997 01:12 | 11 |
| Macros were the problem. I deleted all the macros and now it seems to
work just fine. I'm still a little confused about where they might
have come from since I don't use them (embarassed to admit I don't know
how yet) and I don't get any documents from any sources other than my
own creation ( at least on that particular box). So, once again,
Thanx!!
Ernie
|
| 2915.4 | | QUARK::LIONEL | Free advice is worth every cent | Thu May 01 1997 01:47 | 4 |
| One place they can come from is fax utilities which add a macro so that
you can fax a document directly from Word.
Steve
|