I am developing a website which has a number of staff. The staff are listed on one page in a asp:repeater like so:
Dave Smith
John Smith
Mike Smith
This works great as I can make a repeater and pass over the employee using the old "aspx?id= " and have the next page show the employees details, as most employees have the same categories (education, areas of practice etc..) its been a lot better doing the section this way than doing 10 static staff pages. This is great until..a younger trainee joins the firm. There is just one page with a list of trainee employees and thats where certain trainee name should link to. I have figured this out but I fear it is quite a scummy way and was wondering if their was a more professional way of coding this? at current in the Name section of the database I have placed the full hyperlink, so the table looks like
The system works but as I say is this a complete scumbag way of doing things?
Dave Smith
John Smith
Mike Smith
This works great as I can make a repeater and pass over the employee using the old "aspx?id= " and have the next page show the employees details, as most employees have the same categories (education, areas of practice etc..) its been a lot better doing the section this way than doing 10 static staff pages. This is great until..a younger trainee joins the firm. There is just one page with a list of trainee employees and thats where certain trainee name should link to. I have figured this out but I fear it is quite a scummy way and was wondering if their was a more professional way of coding this? at current in the Name section of the database I have placed the full hyperlink, so the table looks like
Code:
NAME
Dave Smith
John Smith
<a href="trainees.aspx">Derek Smith</a>
Mike SmithThe system works but as I say is this a complete scumbag way of doing things?