>I thought I understood what I was doing until I read this. LOL! If I combine the LDA and RDA into one master data access object (like Jim said) so they can both access the cursor, then there really is no way to replace the form with non-VFP and use the same class code because the class code now has to use cursors. That was my original reasoning behind having the LDA and RDA seperate and having the RDA sent out only XML.

Michelle,

This is NOT true. If I chose to use VB as the UI I would simply publish my data access object (with the LDA and RDA inside of it) as a com object and use CreateObject in VB and call the methods of my data access object to get and set data.

In the case of a web application the data access object could live entirely on the server side. A web hit calls my fox code that uses the data access object to get some data and merge it with an HTML form and serve it up to the client. The client mungs the data and submits it back, my fox code creates a data access object anbd uses it to write the data back to the database.

I could even have the RDA reside on a databse server and the LDA on the web server and have them using XML to move data around. Separating the internal objects like this does not violate my design, it is just a different implementation of my design. Logically the LDA and RDA are parts of the Data Access object even though in the implementation the Data access object does not physicially "contain" the other objects.