Hi John,

I didn't mean this post to discourage you from your solution, but rather as some more information on additional solutions that can be used. There are many ways that this sort of thing can be approached as you're finding out.

+++ Rick ---

>Hi Rick,
>
>Thanks for all the info. I have had this setup running on a total of 7 installations (including some roaming wireless workstations), for about a year now. The only real problem I have is network disconnects.
>
>The 2 COM servers create their own views which remain in effect during the life of the COM servers. They are merely requeried from the main app. For some reason, if a network disconnect occurs and even though the network connection is re-established , all this occurring between any requests for requery, the views in the COM servers are no longer valid and must be recreated.
>
>As long as there is no network disconnects, everything works fine. Even with the disconnects, the COM servers still work fine. It is just the views that are no longer valid. I am trying to find a solution to this.
>
>To get back to your post, to be honest, I have many months invested in this architecture. I will have to stay with it unless moving to SQL causes me to rethink this. At that point I will study your material to see if that is a better approach.
>
>Thanks again,
>John