Suggestion Needed: Best Method for Handling Temporary ADUC Query Data With Multiple Users
I've created a form that allows people to look up user accounts based on first and last name. The data is pulled from ADUC, stored in a SQL table. This includes User ID, Full Name, Acct Description, Creation Date and Last Login.
Table data is pullled in a Gridview that is sortable on each column, allows deletion of individual rows, and even exports data a spread sheet if necessary. I was nearly done, or thought I was when someone asked: What happens if more than one person is in the table at a time? DOH!!! Obviously the answer is that there would be issues. Ultimately only about 10 people would need to use the page, but they wouldn't necessarily be in the same location. So there is a possibility of overlap.
It was suggested that I use an array rather than a gridview. Sounds great, but that would mean starting the whole thing over from scratch. My question: Is there some way to handle this with my existing setup? Like creating a timeout on the page, and not allowing anyone access to the page while someone else is in it? Or do you have a better solution? Any help would be most appreciated.
Thanks in advance!!
Table data is pullled in a Gridview that is sortable on each column, allows deletion of individual rows, and even exports data a spread sheet if necessary. I was nearly done, or thought I was when someone asked: What happens if more than one person is in the table at a time? DOH!!! Obviously the answer is that there would be issues. Ultimately only about 10 people would need to use the page, but they wouldn't necessarily be in the same location. So there is a possibility of overlap.
It was suggested that I use an array rather than a gridview. Sounds great, but that would mean starting the whole thing over from scratch. My question: Is there some way to handle this with my existing setup? Like creating a timeout on the page, and not allowing anyone access to the page while someone else is in it? Or do you have a better solution? Any help would be most appreciated.
Thanks in advance!!
ASKER
The purpose of the page is to allow HR to check for exisiting users in active directory BEFORE putting in a requests for a new account thereby ending the issues associated with employees having multiple accounts created for them.
If the 1st person searches on a last name and gets multiple matching results, they have the ability to sort, delete individual rows, and narrow down the results based on any of the other fields of data mentioned above, or even add other names to the results through a second search.
If a 2nd person accesses the page while they are doing this it will display the 1st person's existing data in the grid below the form. If the 2nd person hits the clear button, which wipes the table, or the delete button which removes a row of data, the change will be noticed the next time the 1st person performs an action that causes a page refresh.
In other words, the 1st person just had their data whacked and wouldn't have any idea what casued it.
If the 1st person searches on a last name and gets multiple matching results, they have the ability to sort, delete individual rows, and narrow down the results based on any of the other fields of data mentioned above, or even add other names to the results through a second search.
If a 2nd person accesses the page while they are doing this it will display the 1st person's existing data in the grid below the form. If the 2nd person hits the clear button, which wipes the table, or the delete button which removes a row of data, the change will be noticed the next time the 1st person performs an action that causes a page refresh.
In other words, the 1st person just had their data whacked and wouldn't have any idea what casued it.
You can add another column to this table to associate records to each user.
ASKER
That's true, but ultimately the way the page is setup it wouldn't prevent them from stepping on each other's toes. Nothing is foolproof to a sufficiently trained fool.
I've created this page for the sole purpose of removing the "we don't have any way to look this info up" excuse before going into a meeting next week. They have ways of doing it, but apparently they don't want to, or can't be bothered to.
The next step will be tracking duplicate account requestors for repeat offenders in order to remove them from the process once and for all. Just tired up cleaning up after people.
Any ideas along the line of only allowing one user at a time or ???
I've created this page for the sole purpose of removing the "we don't have any way to look this info up" excuse before going into a meeting next week. They have ways of doing it, but apparently they don't want to, or can't be bothered to.
The next step will be tracking duplicate account requestors for repeat offenders in order to remove them from the process once and for all. Just tired up cleaning up after people.
Any ideas along the line of only allowing one user at a time or ???
>Any ideas along the line of only allowing one user at a time or ???
That would create more trouble for you. People would keep complaining and it would be hard to implement.
Why dont you build this table in memory?
That would create more trouble for you. People would keep complaining and it would be hard to implement.
Why dont you build this table in memory?
ASKER
The short answer is that I was trying to avoid going to back to the drawing board with very little usable code.
In memory as in using an array or were you thinking of another method?
Thanks!!
In memory as in using an array or were you thinking of another method?
Thanks!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK..... seems like using the data table would eliminate the need for the extra column, and associating the records to each user.
In that scenario, wouldn't the data grid be bound to the data table in memory for each user?
In that scenario, wouldn't the data grid be bound to the data table in memory for each user?
Yes.
ASKER
Thanks for your help!!
What would be the issue with multiple users?