Complexe Manipulation

Gargouil

Hello

I have a complexe question about a database manipulation.

The situation:
I have a little "administrator" search engine, i can search for some people or location. I have a little form where i can choose several options for the search (generally drop list) exemple, one for region, one for country... that not important...

I do a search, and have a list of result, at the moment, no problem. I click on the first of the result list and this open a detailed web page of the element/person/location whatever for edition. I have a Next and Previous button on the bottom to move to the next record.

This is pretty simple if i don'T modify data.

The problem:
Suppose i change and option exemple, the country option, and by search was based on country, the "new search result" should not be the same due to the data i have modified.

The Question:
How can i move with my next and previous button correctly even if i change data...

I use the move next move previous of dreamweaver and i've seen that dreamwaever use the total number of record as variable and move with that... so if the number of record change like my exemple... what sould i do ?

i hope that not too confusing...
i need help, someone please

Thanks
*i don'T want code, just explication will do the job.. i'm not a newbie

mtimdog

Well, you could store the number of records received in a (session) variable.

Then when you edit the record check the number of records against variable.

if the # is the same, then write prev/next as you normally would.
if the # is different, then write prev as you normally would, and write next as going to that same view page #.

This is assuming that your view page is different from your edit page.

Explained:
6 records/pages

1 2 3 4 5 6

Edit record 3 and the # of records stays the same

prev=2, next=4

Edit record 3 and the # of records is one less

prev=2, next=3

Note: this would only work if 1 person is editing at a time, and you have special cases like editing first or last record

Gargouil

Yeah, for a single editing users this seems to be a good way to work, i've done some paper scratch and this work well.

The problem is that more than one person can edit at the same time, not a lot, maybe just 2-3 so.. i need to consider it.

I've think to a possible solution, i can memorize the ID of the last i viewed/edited before clicking next/prev button and make the whole search again, then, finding where is located in the list of record this ID then pick the next or previous one.

I don'T know if it's a optimized way to work, especially because i work with thousand of datas.

Personnaly i don't think there is a solution for this complex problem, so.. i keep hoping 🙂

mtimdog

A nice way I like to work is to have a set # of results per page (15 or db controlled). From that page view/edit, then link back to the results from the view/edit.

This way, change doesn't hurt because the query gets re-run anyway and you can always test for results > rows setting results to rows - results_per_page.