SQL Server 2005 and RDO compatibility

Are tehre any known issues with using RDO with SQL Server 2005?

My company is in the process of updated our SQL Server 7 database to SQL Server 2005. Most of our applications are several years old and written using RDO to access the database. I have since started the daunting task of updating all the applications to ADO, but it's only about a quarter of the way done. We need to update the database ASAP, but we cannot wait until all the applications have been updated to ADO.

While testing the applications (written in VB6) against the new SQL Server 2005 database, I have come across a problem with the RDO queries not returning the correct data. The query returns 4 records. In the SQL7, it properly shows 4 for RowCount and 4 records are present in the recordset (as seen by looping through the recordset using rs.MoveNext). In SQL2005, it properly shows 4 for RowCount, but looping through the recordset shows that the recordset only contains 1 record. The problem seems to be linked to a Left Join in the Query. (see below) Table1 has a column that has a RecID for Table2. In the case where the Table2RecID column in Table1 is 0, the row is just not added to the recordset even though it increments the RowCount.

Code:

---

SELECT * FROM Table1 As T1
LEFT JOIN Table2 As T2 On T1.Table2RecID = T2.RecID

---

I converted the query to ADO and it ran fine with no problems. The issue has something to do with SQL Server 2005 and RDO.

Any ideas, opinions, or anything that might help is greatly appreciated!