Hi again Ahmad,

Under the conditions of how the solution was initially implemented I shall say yes. But remember we have another ways on how to get the work done (querying the database each and every time a user wants to see the Next or Previous member of your guest book sounds inefficient to me).

One could be to provide the browser with javascript arrays containing the guest book members' information only once and program the Previous and Next links to get the current data from the arrays (in this case you would need to access your database only once in your ASP page and generate and fill the client side javascript arrays). Consider that under this scenario the member's info would be visible to the user thanks to the "View source code" browser's option.
Another way could be to load an XML document on the client side to store all the data (again accessing your database only once on your ASP page). In this case you will need the browser to be XML-capable.
A third way that comes to my mind is to play with IIS's capability to define Application and Session variables. You could define an Application variable of array type which could host all the guest book member's info and define a Session variable for every user to keep track which "record" is he currently watching and move around "previous" and "next" records (keep in mind that you need to initialize this variable on the Application_OnStart event in the global.asa file and update it every time a new member comes in or changes its personal info, again this would result in a single access to your database).

We have plenty of ways to get our work done. As always you'll have to decide which is the most convenient for your particular needs. Remember that security, confidentiality, complexity, flexibility and scalability are always factors to consider.

HTH,