It's driving me crazy! Version 4.5 seems to have changed the action of embedded browses.
I have a simple one-to-many set with an embedded browse. The parent record defines an account and the child table is deposits and withdrawals. Every time I make a change in the browse (child table) and save it, the browse jumps back to the top line. Sometimes there is a delay before the jump occurs but it will always happen.
I have also copied the data to new tables with no data dictionary (i.e., no field rules) and created a new set. It still happens even with the default form. I also checked with referential integrity both on and off - same results.
This happens in build 263 and 266 but it does not happen with v4.03. I vaguely recall reading about a change which would affect this but I can't find any reference to it now.
Anybody know of a solution without going back to v4.03 other than opening a new form with just the child table in order to enter data and make changes?
A few minutes later... As I was writing this I thought about another app I have that I don't recall having trouble with. I checked it and it works fine - no jumping to the top of the browse. Any thoughts will still be appreciated. In the meantime, I will see if I can discover the difference in my own apps. I may even re-create the problem app from scratch (it's small) to see what happens.
I have a simple one-to-many set with an embedded browse. The parent record defines an account and the child table is deposits and withdrawals. Every time I make a change in the browse (child table) and save it, the browse jumps back to the top line. Sometimes there is a delay before the jump occurs but it will always happen.
I have also copied the data to new tables with no data dictionary (i.e., no field rules) and created a new set. It still happens even with the default form. I also checked with referential integrity both on and off - same results.
This happens in build 263 and 266 but it does not happen with v4.03. I vaguely recall reading about a change which would affect this but I can't find any reference to it now.
Anybody know of a solution without going back to v4.03 other than opening a new form with just the child table in order to enter data and make changes?
A few minutes later... As I was writing this I thought about another app I have that I don't recall having trouble with. I checked it and it works fine - no jumping to the top of the browse. Any thoughts will still be appreciated. In the meantime, I will see if I can discover the difference in my own apps. I may even re-create the problem app from scratch (it's small) to see what happens.
Comment