Just asking those of you out there who use SPT with an SQL Back End how you handle Grid refreshes (refreshing the underlying data) when browsing tables on the main data server assuming that you may well stay on a browse window when somebody else may well update the data.
I am just trying to write a small set of demo forms using Remote views, Cursor Adapters as well as SPT for Tom here in order to better explain the advantages/disadvantages of each data access method. Obviously with cursor adapters you can issue a cursorRefresh() against the back end and with remote views you can do a requery() against the view. The only method I use with SPT is in fact to issue the "select..." again. Anyone got any better suggestions apart from using stored procedures on the back end which I don't really want to use. The nice thing about the remote view and cursor adapter method is that the currently selected row gets preserved in the grid. I have tried the same in SPT by saving the current row and navigating to it after the re-select but it causes screen glitches regardless of using _Screen.Lockscreen unless anyone else has a better idea! Dave --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ 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.
