Good morning, Bob.

When debugging, take a look at the recordset Fields collection, i.e.,

de.rscmdJobList.Fields(0).Name
de.rscmdJobList.Fields(1).Name
.
.
.
de.rscmdJobList.Fields(n).Name


What's in there?

Also, do you have some flavor of error handling turned on, like On Error
Goto Whatever ???

ADO shopuld give you much more error information than "[error]"

I believe the Connection object has an Errors collection.  

Here's a routine to get VB to spit out the ADO Errors collection:

http://msdn.microsoft.com/library/psdk/dasdk/mdae0i60.htm

Regards,

John Covert
Accountable Software
xxx.xxx.xxxx  x16
mailto:JohnC@A...

Accountable Software, Inc.
http://www.accountable.com
412 Creamery Way, Suite 100
Exton, PA  19341-2500
Tel:  xxx.xxx.xxxx 
Fax:  xxx.xxx.xxxx

2000 Accounting Today Technology Pacesetter
2000 Deloitte & Touche Technology Fast 500
1999 & 2000 Excellence in Integration Award
Great Plains 1998 Global Developer of the Year



-----Original Message-----
From: Bob Clegg [mailto:bclegg@c...]
Sent: Monday, March 05, 2001 5:55 AM
To: Interdev_Programming
Subject: DE Parameterised commands


Hi,
I have a 'select' command object in my data environment that takes one 
parameter to filter its recordset.
I can't see how to access the resulting recordset in the ASP page script.
eg 
de.cmdJoblist lngStaff
de.rscmdjobList.movefirst
While not de.rscmdJobList.eof
	strDes=de.rscmdJoblist("strDescription")
...

Using the debugger, the code steps into the while loop and executes the 
string assignment, but if you print the string in the immediate window it 
contains [error]
The filtering appears to work because when lngStaff is chosen to give an 
empty recordset return, the while loop gets bypassed.
Any help would be appreciated.

thanks
bob