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.

I think at this point, I'm going to stick with what I have. It's a small enough project that if we would ever have to change the front end, it wouldn't be terribly hard to re-write. Trying to learn how to do things right has taken way too much time and I really need to stop re-arranging the code and get it done.

I'm not saying I'm giving up learning proper OOP. Just that for the purpose of this project, what I have will work fine.

Thanks for your help, and I'll still check out that article. :)

Michelle

>Of course it is alright < s >. It makes sense that a VFP front end should access the cursors directly because this is the most efficient way to do it. That does not impact the ability of your business object to be able to dish up this data into other formats (XML or ADO) for other front ends as required.