taersious

You would not need to provide a preventDefault() call if you were not using a button with a type attribute of "submit". Just use type="button" for such cases when you do not intend to submit the form.

Personally I would use the database object solution, in which the library of possible name prefixes, suffixes, and so forth would come from a table. Obviously used names would be in a seperate table. When generating name at random, make sure potential new name is not already in existance. Good …

You never gave a name for the name of the result textbox. Problem with trying to help is that there are so many different ways to give you what you ask. ASP.Net allows us to create new instances of page objects (textbox for example) which you can then apply properties. …

It is posible, but memory may limit how many lines you are able to store in memory. I would recommend reading the data into a physical HTML table object (not shown on screen).

You are correct. You are simply appending the same current value repeatedly. To solve this, you are going to need to store your previous entries in ViewState, Session, or other form field such that your values aren't lost between Postbacks. Cheers.

If you have something like `<div id='output'></div>` Then you could do this: function getFavourite() { var name = document.createElement('a'); var linkText = document.createTextNode("Student 1, "); name.appendChild(linkText); name.title = "Student 1, "; name.href = ""; $("#output").append(name); }

Make sure you have the property set to 'copy local' or include an item in this folder in your project and then republish.

I would tie into the jQuery object id or class (if the class is a singleton) and solve this on clientside. You would have to provide your code base to get further suggestions on exactly how javascript would be utilized to solve it. Cheers!

One option is to not generate these controls on button click. Have them already present in the design, and set the visible property true/false depending on your logic. This way, the page will allow your objects to persist between postbacks.

You would need to place this logic in every page which needs this funcionality. A better option would be to move this logic to your Site.Master.vb file and allow the MasterPage to control this funcitonality. This way you would not be repeating the code in each page, which it one …

You might take a look at http://softvelocity.com/Community/Usergroups.htm I found this post while I was looking for this myself. -Drew