Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Record Pointer Best Practice
Message
From
27/07/2001 15:40:52
Gerry Schmitz
GHS Automation Inc.
Calgary, Alberta, Canada
 
 
To
27/07/2001 09:55:37
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00536306
Message ID:
00536645
Views:
9
>There are likely some architectural flaws in the following reason, but I use views to pull a subset of records (View1) from the base table, then pull another view from the base table (View2) based on criteria for the selected record in View1, then finally pull the record to edit (View3) from the base table based on the selected subset record in View2. When editing (or whatever) is done, I want to return to the last current record in View2 and subsequently return to the last current record in View1. What would be the best way to handle this?

I'm probably missing the big picture, but I use "Session classes" to handle multiple views; ie. the View is wrappen in a Session class.

When I have a Form or something that is "data driven" I just point it to the DataSession Id of the Session Class (ie. "View" ) in question.
Previous
Reply
Map
View

Click here to load this message in the networking platform