if June is correct and you want to break up both the svccode and the svcdescription you'll have to do it with VB script.
What june means by normalizing is that you appear to be carrying a lot of duplicate information from table to table which you do not need.
For instance (just based on the information you're showing) I would have the following tables:
Code:
tblPeople
PeopleID FirstName LastName DOB
1 Bob Smith 1/1/2011
2 Jane Doe 1/1/1900
Code:
tblServices
SvcID SvcCode SvcDesc
1 123 Cat
2 456 Dog
3 789 Watermelon
4 1010 Chinese Lantern
5 989 Beach
6 1212 Chicken
Code:
tblOrders
OrderID OrderNumber PersonID
1 0001 1
2 0002 2
Code:
tblOrderItems
OrderItemID OrderID SvcID PeopleID
1 1 1 1
2 1 2 1
3 1 3 1
4 1 4 1
5 2 1 2
6 2 5 2
7 2 4 2
8 2 6 2
All of my ID fields are for the purposes of this example autonumber fields.
In this way you eliminate the variability of people typing in extra comments or misspelling words in your data entry, you can limit their choices (on services) a pre-determined list which they can not deviate from. You can provide for comments (i.e. 'ordered by me' 'it's so cute') if you want to instead.
All this being said there is a way to parse your information but it will involve putting the information into a different table before you can use it and finding out whether it's possible to have fewer or more than 4 entries per line, that's pretty critical when programming a solution. Or at the very least knowing what the maximum number of SvcCodes/SvcDescriptions one can have in those fields (and assuming nothing in the svcdescriptions has a comma)