There is no message.. Just the data isn't displayed.. IT's like the recordset went away or something.. I'm going to try what you gave me.. I wasn't using the command object, and maybe that'll help. I'll definately be porting some of this same codo to ASP pages, will it always behave the same as Fox? I ran the same test on my IIS server with an ASP page and it didnt return an error either, and still no data.

Thanks. I'll try this out and see what happens.


>When you say it fails, what OLE-DB Error message do you get?
>
>The following is a revised version of your code:
>
>oConnection = CreateObject("ADODB.Connection")
>oCommand = CreateObject("ADODB.Command")
>With oConnection
> .CursorLocation = 3 && Client-Side Cursor
> .ConnectionString = "DATABASE=PROGLIB;DSN=DDHELP;UID=someone;PWD=;"
> .Open
>EndWith
>With oCommand
> .CommandText = "Select * from programs where rtrim(ltrim(progrm_key)) = ?"
> oparameter = .CreateParameter("v_progkey",129,1,1,"1")
> .Parameters.Append(oParameter)
> .CommandType = 1
> .ActiveConnection = oConnection
> oRecordSet = .Execute
>EndWith
>
>?oRecordset.Fields.Count
>
>For Each Field in oRecordset.Fields
> ?Field.Name,Field.Value
>Next Field
>
>For starters, if you are using SQL Server, I would HIGHLY recommend using the OLE-DB Provider, NOT the OLE-DB Provider for ODBC.
>
>Things to verify:
>
>1. The number of fields in the Recordset
>2. The names of the fields in the Recordset
>
>
>Good luck,