A Refreshing Idea for Refreshing a Browse
Maybe I lost my sanity!!
Get this..Your world gets turned upside down with Katrina, all the routine, all the organization, all the perfections your entire world gets thrashed around, literally, all the rules of the game get thrown out of the window. You have no idea what are the new rules that's if you are luck enough to figure out the new game and in the midest of all of this madness where you line up for the basic necessities of life, what do you do?? you go to the message board and start a new topic!! You are going crazy, that's for sure!
Maybe. Or maybe it's a diversion, an escape and possibly a therapeutic maneuver...
So to get away from it all and while I have few moments on a friend's computer, I did a quick scan of the good ole board, and don't you know it? the same subjects keep popping up.
Then I decided to share one of my "tricks" with you, I believe it will bring you joy and happiness.
It has to do with the nagging subject of refreshing an embedded browse.
Suppose you have a form based on a set with an embedded browse. You add a record to the embedded browse, and the darn thing will not show up no matter what. Or, conversely, you delete a record and it stays there.
This causes a lot of frustration to just about every one, and what is more frustrating is the fact that:
a-a lot has been written about this and while many suggestions were made, some are drastic and most acknowledge that they do not work 100% of the time
b-Everyone was waiting for alpha's new version with the hope of overhauling the browse were this is no longer an issue.
Most were disappointed when alpha put that on hold. Not me !! since I used this trick, it has not been an issue anymore.
I haven't introduced this sooner because I wanted to try it for long enough time to make sure it works consistently.
It does.
It's so simple, one of those things that make you wonder: Why didn't I think of that before?
Here is what you do:
After you add your new child record, do the following:
1-activate any field in the parent table, any one.
2-activate any field in the child table, any one.
That's all.
Your child record will be there.
In case of delete, you might want to add another line to cancel changes.
Gabe.
P.S.
If you reply to this, and I wish you do as I would like to hear your feed back, and if you do not hear from me, it's because I have access to the internet only occasionally when visiting someone who has this great privilege.
Next trick: progressive lookup on a dime.
Maybe I lost my sanity!!
Get this..Your world gets turned upside down with Katrina, all the routine, all the organization, all the perfections your entire world gets thrashed around, literally, all the rules of the game get thrown out of the window. You have no idea what are the new rules that's if you are luck enough to figure out the new game and in the midest of all of this madness where you line up for the basic necessities of life, what do you do?? you go to the message board and start a new topic!! You are going crazy, that's for sure!
Maybe. Or maybe it's a diversion, an escape and possibly a therapeutic maneuver...
So to get away from it all and while I have few moments on a friend's computer, I did a quick scan of the good ole board, and don't you know it? the same subjects keep popping up.
Then I decided to share one of my "tricks" with you, I believe it will bring you joy and happiness.
It has to do with the nagging subject of refreshing an embedded browse.
Suppose you have a form based on a set with an embedded browse. You add a record to the embedded browse, and the darn thing will not show up no matter what. Or, conversely, you delete a record and it stays there.
This causes a lot of frustration to just about every one, and what is more frustrating is the fact that:
a-a lot has been written about this and while many suggestions were made, some are drastic and most acknowledge that they do not work 100% of the time
b-Everyone was waiting for alpha's new version with the hope of overhauling the browse were this is no longer an issue.
Most were disappointed when alpha put that on hold. Not me !! since I used this trick, it has not been an issue anymore.
I haven't introduced this sooner because I wanted to try it for long enough time to make sure it works consistently.
It does.
It's so simple, one of those things that make you wonder: Why didn't I think of that before?
Here is what you do:
After you add your new child record, do the following:
1-activate any field in the parent table, any one.
2-activate any field in the child table, any one.
That's all.
Your child record will be there.
In case of delete, you might want to add another line to cancel changes.
Gabe.
P.S.
If you reply to this, and I wish you do as I would like to hear your feed back, and if you do not hear from me, it's because I have access to the internet only occasionally when visiting someone who has this great privilege.
Next trick: progressive lookup on a dime.
Comment