A stored procedure which performs an insert from an MS Access table (itself
linked to a Pervasive database) and then performs a series of update queries
to sanitise the data runs fine when invoked from a query window.
In order to regularly run this stored procedure on a schedule, it is set up
as a one-step job. The job fails, returning a message:
provider "Microsoft.Jet.OLEDB.4.0" for linked service "(null"). The specified
table or view does not exist or contains errors. [SQLSTATE 42000] (Error
7306). The step failed."
The query which appears to be generating the error is an insert query:
INSERT INTO Table (field1, field2,...)
SELECT field1, field2...
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0', '[path]'; '[user]'; '[password]',
Table) As Alias
As I said, this query runs fine when invoked from a query window, but
returns the above error when run as a one-step job. DOMAIN\user has full
What is the difference between a query window and a job that would cause this?