Any have a suggestion as to the best way to do this? I'm entering data into a SQL database on customers - each customer's unique identifier (i.e., the primary key in the db) is what's called a BTN (business telephone number) with a "cust. code" (customer code) at the end of it. I use these 13 digit numbers EVERYTHING. Now, here's the problem. I'm doing an interface for a customer survey - the people entering the survey information have been using a system that for 30 years has split the BTN/Cust.Code into 4 sets of numbers (area code, nxx [that's the 3 digit number before the dash], customer line [four digits at the end of your phone number], and customer code) - and they're being <b>very</b> adament about that being the only way they'll enter the numbers into any survey...ok...anybody know a good way to concatate the four seperate numbers into one column which is the primary key, while still having four seperate fields (I can actually use the idividual area codes seperate) containing the elements of the numbers. By the way - thanks Cheech and LadyBorg - you guys have been saving me a whole lotta stress.
Cyberpunk Scott Neth
Web Designer/Cyberpunk
Cyberpunk Scott Neth
Web Designer/Cyberpunk