Don't do it. You can, it's not difficult - beginners do it a lot with a column containing comma separated values. But ... it's a poor idea because while it's easy to insert and trivial to code, it gives huge headaches down the line, by which time it's too late to change it and you have to live with the problems.
For example, suppose you have three values separated by '|': "John Smith|12 Green Lane|Morcombe" That works fine and it's easy to use Split in C# to separate them. But what happens when he moves to Peach Pie Street? To change it, you have to pull the row from the DB, split it, change the string, re-join it, and push it back to the DB.
Instead of that, create a second table:
ID CustName CustAddress CustTown
1234 John Smith 12 Green Lane Morcombe
You then include a Foreign Key column in your main table with refers to this by the ID column.
When you want to change the address, you just issue an UPDATE to the DB referencing the correct ID, and it's done.
And when you want to get the info, you use a nice simple SELECT with a JOIN and you get the relevant data in separate columns, ready to be bound to the textboxes directly.
Submit an article or tip