Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
General information
Title:
Record Pointer Best Practice
What are the opinions regarding how to store and then use a record pointer for numerous views in an app? I was starting to create properties for the form based on what the current view's recno() was, but then thought there was probably a better, scalable solution.
Let's say for example that I currently have only two views, View1 and View2. I would create form properties called CurRecView1 and CurRecView2 and then store/reference as needed. If I add more views later I will need to add additional like properties. I also use a form property called CurView that holds the alias name of the current view (or the view current when the property is assigned anyway). The problem comes up sometimes when I run save routines and such that I endup having to reference the CurRecView1 and CurRecView2 properties. Things start becoming tangled if I have more views and trying to keep track of all the pointer so that I return to where I was when I left to do something else (with other views).
If my post isn't very clear then you see this the way I do. :) Thanks!
Regards, Renoir
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only