J
Jon Ley
I have an Access XP database (compiled as mde) being used under the run-time
version. Development environment is Access XP SP3 running on XP Home SP2.
MSAccess.exe run-time on the clients reports version 10.0.2627.1. There are
various clients, some using the database locally, some over Terminal
Services. The ones running Access locally are fine, however the clients using
TS keep crashing immediately after printing some of the reports. The reports
do get printed, but Access dies straight away after the printing code has
run. This only happens if the reports are opened with vbNormal (or with no
option specified - i.e. DoCmd.OpenReport "ReportName"). If the reports are
first opened in preview mode and printed from there then the program does not
crash. The 'crash' is the old 'Microsoft Access has encountered a problem and
needs to close' etc, with options to repair the database and re-open Access,
and to send or not send an error report.
I have tried a couple of things. I have tried not using DoCmd.OpenReport
(instead use DoCmd.SelectObject and then DoCmd.RunCommand acCmdPrint). I have
tried removing the modules behind the reports (used to Maximise and Restore
when opening and closing the report). I have tried creating a new database
(with name autocorrect options turned off) and importing all objects from the
problem one to make sure that there was no rogue code hanging around. None of
this has made any difference.
Any suggestions gratefully received.
version. Development environment is Access XP SP3 running on XP Home SP2.
MSAccess.exe run-time on the clients reports version 10.0.2627.1. There are
various clients, some using the database locally, some over Terminal
Services. The ones running Access locally are fine, however the clients using
TS keep crashing immediately after printing some of the reports. The reports
do get printed, but Access dies straight away after the printing code has
run. This only happens if the reports are opened with vbNormal (or with no
option specified - i.e. DoCmd.OpenReport "ReportName"). If the reports are
first opened in preview mode and printed from there then the program does not
crash. The 'crash' is the old 'Microsoft Access has encountered a problem and
needs to close' etc, with options to repair the database and re-open Access,
and to send or not send an error report.
I have tried a couple of things. I have tried not using DoCmd.OpenReport
(instead use DoCmd.SelectObject and then DoCmd.RunCommand acCmdPrint). I have
tried removing the modules behind the reports (used to Maximise and Restore
when opening and closing the report). I have tried creating a new database
(with name autocorrect options turned off) and importing all objects from the
problem one to make sure that there was no rogue code hanging around. None of
this has made any difference.
Any suggestions gratefully received.