We had a great Christmas thanks. Lots of goodies and good times! Did you get snow :-) ?

Back to business...
We have a toolbar option which calls up some user specific saved data in a browse screen from anywhere within the app. We wanted to allow the user to move next/prior in that same data in a very generic way while it's linked to the form data. So imagine a list of names from a report or query, which includes a key field. We are allowing users to bind to that ad-hoc data from the names screen and navigate the names based on a candidate key in the ad-hoc data. The same applies to any other main data modules, like orders, invoices, receipts, quotes, parts etc.

I've ditched the right click idea which was going to have a last/next/prior/first type shortcut menu in favour of a picture check box on the form which remaps the normal navigation buttons in the form to do the same thing. So the user can choose to navigate normally or lock onto the ad-hoc data. Kinda like setting a filter.

The users are quite excited about it - imagine any report or browse screen (we have hundreds) being able to be linked to any appropriate data screen. For example a list of unprocessed jobs, outstanding debtors over 120 days, quotes that haven't had responses. They are currently using a version without the linking, which they already love. This will be icing on the cake.

All the best

>Hi David.
>
>Anyway thanks for the tip on Objtoclient().
>
>Actually, I think I hit send way too fast because I do not think that it will help you in this case. Sorry about that!
>
>I'm not even sure I want to use right click on a toolbar. It's not a very obvious thing to a user. How do I best provide options on a toolbar button?
>
>I have to agree with you there. It would not occur to me to right click on a toolbar button.
>
>What are you trying to accomplish here? I am not sure I understand what you mean when you say "provide options on a toolbar button"
>
>Merry Christmas to you!
>
>Same to you! I hope Santa brings you everything you want this year.