I understood that that is what the code asked for. Don't blame VB. And I do not really wish to know how many dynamic cursors are used where...

Those parameters mean a dynamic cursor. I changed @p2 that is the scroll-options to static or forward-only and @p4, that is the concurrency option to read-only it works fine....

There seems nothing strange in the source.

I found something new. If I take the sum out the statement, like below it works fine:

declare @p1 int

set @p1=0

declare @p3 int

set @p3=229378

declare...

noeld (10/5/2007)

---

Not entirely sure but you should check client side code for any unhandled exception. The "missing cursor declaration" part is a hint that something is not working properly on...

With openrowset() and openquery() you can access the file directly. See the BOL for details.

In case someone else has the same problem.

I contacted Microsoft through the metro program (beta program for ISV's) . It seems the line continuation, underscore at the...

This is true for SQLServer 2000.  SQLServer 2005 has "database mail" which uses SMTP.

The developer seems to be happy making a ODBC connection for this action.  Not really a solution, but a workaround.  With Oracle there is no problem. 

Just trying things,  both cursors were set to static and that resulted in the following error:

Microsoft OLE DB Provider for SQL Server' 0x80004005 Cannot create new connection because...

No.  You have the check "enforce password expiration".  If you uncheck it it will last forever. It is just that if you do nothing it is checked.

Replacing * with fieldnames has no effect.

The DSNless connection gives a usefull error message:

DBArecordSet.OpenSet Error from: 'Microsoft OLE DB Provider for ODBC Drivers' 0x80004005 Unspecified error Native: 0 (help=.0)

DBArecordSet.OpenSet...

I think it is because the code is preformatted.

SQLServer will deny access if you have "Enforce password expiration" enabled.  mydbuser will not expire.  sa default will.  If you unchecked "enforce password expiration" it will not.  I take care...

Both SQL statements where entered with:

ADODB.RecordSet.Open strSQL, aDBcn.Connection, adOpenForwardOnly, adLockOptimistic, -1

I allready sent you all the error messages.

The program produced the following (self programmed) trace:

06-11-2006 15:01:43 DBAaccess.StartLUW...

You will need to join with both sysjobschedules and sysschedules.

Or just be lazy and use sp_help_schedule