1. Clients have data sets which are located in various physical locations.
2. The data source for the grid must be created with the client data once the client has logged in.
3. The data source for the grid must further be unique and scoped to the user session.
4. The grid must function smoothly and not get reset with each request it must appear to the user just like on a desktop where they can manipulate the grid at will, call subforms, etc. with no visible disruption.
5. The data can be updated to the master tables once the user selects to close the grid.
All this is not hard except for the fact that the grid makes it near impossible.
-Views cannot pre-exist since cleints cannot share data or database containers.
-using cursors or temp tables will not work because the data source is not scoped to the session
-so if you do scope the data to the session, it requires resetting the grid recordsource every request and every time any grid data is updated. That destroys the usability of the grid.
So far no proposed solution works, so I am open to all ideas.