I would guess a bug in Access, rather than anything else.
0) Check the data: make sure none of the data fields
show 'error': Check to see if Null, Zero, or Missing data
is causing a problem: Check for inappropriate data in
text fields.
1) Use the /decompile command line option for MSACCESS.EXE
to decompile the MDB.
2) Re-compile and save
3) Don't use code that includes deliberate throws to an error
handler.
2) Make sure you attempt to export to file without Word 'autostart'.
3) See if you can build a simpler report to use with the Word
export.
4) Probably not an issue with Windows/Office 2000 as such,
(there should be no overlap with Office 2000, and successive
versions of Windows actually handle COM and Memory better,
leading to fewer problems like this) but still possibly a machine
configuration problem of some kind.
(david)
siglerr said:
I work with several other facilities on a help desk. The company that I
work for has written an access program that uses standard programming. I
have three place that have the same problem. With the company program a
report is generated and display in preview mode before itis printed. The
user would like to use the office tool to send the report to word. When this
is done a Dr. Watson error occurs and access shuts down. The report has
several sub reports in it. The office link will work with other reports that
access generates and when running a query the query results can be sent over
to word with no problems. Wondering if this is a corrupt dll file, incorrect
install of access or an issue with windows and/or office 2000?
