Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Best practices for app server in multi locations
Message
 
To
22/07/2006 18:21:10
General information
Forum:
Visual FoxPro
Category:
Client/server
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Miscellaneous
Thread ID:
01138155
Message ID:
01138842
Views:
9
I'll start reading your articles. Thanks

>That's why you use queued components. The update is automatically saved by Windows and then sent once the connection is available.
>
>>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
Previous
Reply
Map
View

Click here to load this message in the networking platform