>Depending on how your application is designed now, you may need to do that anyway to move to SQL Server. If you've been using local views as your only way to access the data, then moving to remote views will be easier. If you use any other way to access the data (SEEK, LOCATE, APPEND BLANK, APPEND, etc), then you'll need to do some redesign.
>
>>Thanks. The recommendation is great. I'm going to read your articles.
>>But, recognizing that I'll need to redesign the complete architecture of my app is what's giving me a pit in my stomach.
>>Cheers,
>>Allen

It shouldn't be too much trouble since I work with temp cursors primarily, and just write back to the tables. I could change the tables to remote views, instead.
I was thinking it would be a harder thing to redesign a disconnected database arrangement. If the user needs to save changes (or lookup new information), what should occur if the connection is not available (in the unlikely event, of course).
Is the best practice to save to local tables, and sync up at various intervals? What a PITA to manage.

Allen