Hi John;

The recordset was generated using a command object. I moved the text field to the last field in the table and now it works fine.

But that was Thursday. On Friday I was populating a recordset using a moderately complex query (with a command object) and ran into the wacky behaviour where ONE field of the recordset always carried a NULL value after doing a movenext. All other fields had the correct data. Debugging ASP is not fun, but I could follow this behaviour, though no reason why. I moved the query into a stored procedure (exact same definition, except for the parameter) and now it works!

These 'quirks' remind me of the quirks of DBase IV which made Fox seem like heaven because it worked so well.


>Actually, if you use a stored proc/command object as the basis of fetching/retrieving data, and rely on a RS as only a way to move data around, you won't have a problem... The RS sucks as a way of updating data. In reality, the RS uses a command to do the updating. However, by using the RS itself, alot of implicit actions occur. Best to make great use of the Command Object.
>
>It's not nonsense...Rather, it is a matter of understanding how this stuff works. Like everything, ADO has it's quirks.