My general approach to data (remote or otherwise) has been to set up an object hierarchy in which each object maintains its own data. I work for a school, so we have families who have students on our program, who then have grade levels, which have courses, which have quarters, which have individual assignment grades, etc. I have never worked with remote views because the objects don't need them. We use a combination of postgres and foxpro to store most of the data. For most tables the data starts in Foxpro and then uses a trigger to automatically replicate to a postgres table, giving us an instant backup. Most queries are done against the postgres data, since that is usually much faster than querying the FoxPro data.
