Does the old app move the record pointer or attempts to lock the record when it refreshes data? Otherwise you will never see the changes being reflected no matter what SET REFRESH is set to. If you can't change the code extend your test to navigate to a different record in the old app and then back to previous one after changing the record in the new app. You should then see changes in the old app. If not, this would indicate that the old app is using table buffering and you changed a field in the record.
Christof --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cal4qjhipgvxzg-pb825u21fdz23xjmrzdrqqrgwo-8dhv2r...@mail.gmail.com ** 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.
