Scheduled Job Running MS Access in Background not Foreground

We had a scheduled job, within it a step would run an Access app. Before Ac
cess would pop up, and if it errors out it will shut itself down and the job
would see it as an error and try and rerun the Access app.
After migrating to a new server (install is identical except for hardware),
the Access app when called from a job will run in the background, meaning yo
u can only see that it's running by going into the Task Manager and going in
to the Processes tab. Also
now when Access errors out, (in the background there is a dialog box indicat
ing an error in Access and someone has to go and click ok, which can't be do
ne, since Access is running as a background process) it will sit there waiti
ng for someone to click OK
on the error dialog box. The scheduled job will just hang there since the j
ob thinks Access is still running.
Does anyone know how to get the job to NOT run the Access app in the backgro
und and to know when Access errors out?Can't you just write code to catch the error in the Access database?
"ckaneko" <anonymous@.discussions.microsoft.com> wrote in message
news:DB4CB092-B1B9-4388-9780-EFDCFC9052DB@.microsoft.com...
> We had a scheduled job, within it a step would run an Access app. Before
Access would pop up, and if it errors out it will shut itself down and the
job would see it as an error and try and rerun the Access app.
> After migrating to a new server (install is identical except for
hardware), the Access app when called from a job will run in the background,
meaning you can only see that it's running by going into the Task Manager
and going into the Processes tab. Also now when Access errors out, (in the
background there is a dialog box indicating an error in Access and someone
has to go and click ok, which can't be done, since Access is running as a
background process) it will sit there waiting for someone to click OK on the
error dialog box. The scheduled job will just hang there since the job
thinks Access is still running.
> Does anyone know how to get the job to NOT run the Access app in the
background and to know when Access errors out?