J
JohnE
Wow. Just had the boss stop and give me what he wants to do as it comes to
those who submit requests. When a person submits a request, generally they
prioritize it (1, 2, 3, etc) based on their other submitted requests. This
priority number is stored in the db. It is possible that a user will review
their requests and want to reorder them. This is where the boss comes in.
He is looking at a method that will show a user all of their requests, and
eventually others, in priority order and allow the user to move (drag and
drop) the request and have it reprioritized (numbered) based on where the
user drops it on the list. The only one that I can think of as an example of
what he described is the Netflix que has this. Granted, theirs is not
Access. So, I am wondering if anyone has ever done something like this or
know of examples/samples to view?
Thanks.
John
those who submit requests. When a person submits a request, generally they
prioritize it (1, 2, 3, etc) based on their other submitted requests. This
priority number is stored in the db. It is possible that a user will review
their requests and want to reorder them. This is where the boss comes in.
He is looking at a method that will show a user all of their requests, and
eventually others, in priority order and allow the user to move (drag and
drop) the request and have it reprioritized (numbered) based on where the
user drops it on the list. The only one that I can think of as an example of
what he described is the Netflix que has this. Granted, theirs is not
Access. So, I am wondering if anyone has ever done something like this or
know of examples/samples to view?
Thanks.
John