Heard from client's Tech guy. Apparently the Server 2016 has been in
place for awhile. No problem when my app accessed from Windows 7
clients; problems only started with the introduction of the Windows 10
clients.
On 2017-06-06 17:18, Fred Taylor wrote:
Sounds like a caching issue.
Fred
On Tue, Jun 6, 2017 at 1:49 PM,
<[email protected]
wrote:
VFP9SP2 app on Win10 clients; data on Windows Server 2016
Client showed me (via TV session) how adding records seems to show the
new
records in the local vfp view, then after saving, not showing them,
then
exiting and re-entering the app, the data is there. Now normally we'd
say
"well it must be a bug in the app" -- but this app has been rock solid
and
bug free with this basic add operation for 14+ years now. The only
change
in the environment is the new Server 2016.
Anyone having any issues with their VFP DBC tables residing on Windows
Server 2016?
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
