Just another thought. You can try a direct connection bypassing the DSN.
This is from the manual with amendments
" In cases where you do not have control over the ODBC control
panel to set up a DSN for your database or where you may want the
higher efficiency, you can connect to a datasource wihtout using a
DSN. Instead of using the URL syntax, a block is pased to open. The
block has the following syntax:
connect-name: open [
scheme: 'odbc
target: join "{DRIVER=3DMicrosoft Access Driver (*.mdb)}; "
"DBQ=3Dc:\Databases\mydb.mdb"
]
where SCHEME is always set to 'odbc, and TARGET is a complete
connection string defining the datasource, driver, and any other
needed parameters. The example above uses a Micrsoft Access database
and driver. Any number of standard and driver-specific parameters may
be passed in the target string."
On 9/7/05, Graham Chiu <[EMAIL PROTECTED]> wrote:
> At this point, I suspect it because your scheduling application does
> not have the same user rights as when you run it yourself.
>=20
> Now this is beyond my experience, but is it a system DSN or a user DSN?
>=20
> On 9/7/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Yes, I can start cmd and run the script successfully with the command C=
:\Rebol\rebolcmd.exe %/C/Rebol/deltdlrows.r.
>=20
> --
> Graham Chiu
>=20
--=20
Graham Chiu
--
To unsubscribe from the list, just send an email to
lists at rebol.com with unsubscribe as the subject.
