We're building an application which, when a report runs and contains
no data, issues a message to inform the user that the report has no
data.  The macro that issues the message then does a CancelEvent to
cancel the report.  It works fine under Windows 95b and 98.  When it
runs under Windows 2000, it causes an OS error because the print
queue has been cancelled.
Does anyone know of a way around this problem?