It's pretty obvious at this point that I am completely lost. I'm going to try reading Markus' book this weekend and hope something clicks. You guys have tried to explain things to me, but I'm getting more and more confused. There's a limit to how much teaching I can expect from people on the UT and if I ask anymore questions, I think I will be past it. So I'll take your posts, take the book, and do some clue searching myself. :)

Thanks,

Michelle


>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.