Re: Lost Query - Bug or Expected
Donald
Had a look at your sample attached to the other post.
I would say what you are experiencing is not a bug.
When the form first opens, the base filter on the form is activated and Shippingticketno 4 is shown as it should be.
If at that time you load the companion browse you will see that the order is 4 3 2 1.
Now when you go back to the form, and then enter a new record and then cancel it, the form now shows shippingticketno 1 which is the last record by filter in the table. When you cancel it goes to the last record which is shippingticketno 1.
If you change the base filter to ascending and open the form - shippingticketno 1 will be shown based on the filter. Enter a new record and then cancel, then the last record in the filter will be shown which is shippingticket no 4 - which is what happens.
Now back to the invert(shippingticketno) as the base filter, if you use query by form and say select shippingticketno 3. That will be shown on the form, then if you call the companion browse it will only show the result of the query which is shipping ticket No 3. Just as it should. Now when you switch back to the form it again will load to the query which is shippingtickeno 3.
It seems to be working as it should.
FWIW
Tom
Donald
Had a look at your sample attached to the other post.
I would say what you are experiencing is not a bug.
When the form first opens, the base filter on the form is activated and Shippingticketno 4 is shown as it should be.
If at that time you load the companion browse you will see that the order is 4 3 2 1.
Now when you go back to the form, and then enter a new record and then cancel it, the form now shows shippingticketno 1 which is the last record by filter in the table. When you cancel it goes to the last record which is shippingticketno 1.
If you change the base filter to ascending and open the form - shippingticketno 1 will be shown based on the filter. Enter a new record and then cancel, then the last record in the filter will be shown which is shippingticket no 4 - which is what happens.
Now back to the invert(shippingticketno) as the base filter, if you use query by form and say select shippingticketno 3. That will be shown on the form, then if you call the companion browse it will only show the result of the query which is shipping ticket No 3. Just as it should. Now when you switch back to the form it again will load to the query which is shippingtickeno 3.
It seems to be working as it should.
FWIW
Tom
Comment