problem scheduling access 2000 database

[jc]

I am attempting to run an access database via a bat file using TWS (Tivoli
Workload Scheduler) on a windows 2003 server. In the bat file I have

"d:\microsoft office 2000\office\MSACCESS.EXE"
d:\vis_db\unixmgmt_2000\unixmgmt.mdb


there is an autoexec macro in the database that kicks off when you open it.
I can run the bat file fine myself from the command line or by double
clicking it in windows explorer, but when TWS runs it, it starts access and
opens the database but none of the commands get executed, it just hangs. any
idea why this would be? I thought it might be a security problem but all the
directories that the code touches, have full control permissions for the ID
that TWS is using to run the bat file.

 

[Wayne-I-M]

Hi

Prob isn't it but it may be that the exec is set to do just this. You could
try resetting the autoexec. If you can get in try....
Tools
Option
View
Hiden Objects

If you can't get in try
Secutrity
User Permissions
once there reset and change then change autoxec

As I said prob not this but worth a try

 

[George Hepworth]

This post was submitted by someone known to be masquerading as a well known
and highly respected Access MVP.

George

 

[Tom Wickerath]

you don't need to schedule anything like that
you need to use SQL Server and Acces Data Projects- which has it's own
scheduler called 'SqlAgent'

why reinvent the wheel?

 

[jc]

I don't think this is the issue because when I run it myself by just opening
the database and/or running the bat file from the command line it works. it
seems to be isolated to when I try to run it from the scheduler.

 

[David S]

Has anyone found a solution to this problem?

I have the same issue when trying to run a module using Task Scheduler. It
runs fine if you're logged in, but the task seems to hang after it opens the
..mdb. The step it stops at involves importing data into an existing table.
It runs if the account used to schedule the job is logged in, so it isn't a
rights issue.

Issue with Access perhaps?