Maybe I'm just missing it... what does the output you listed have to do with the query you listed?

The problem with such "real time" apps is that no one plans on the connection being down Have your "trigger" write to a...

Kind of a double post... please see my other reply.

Don't embed the quotes... put the quotes around each full path.

Oh no, no, no... MJV had it right and ISNUMERIC does NOT mean ISALLDIGITS!

create table #tmp( tc VARCHAR(10))

insert into #tmp

select '0d01' union all

select '0e01' union all

select...

Yep... then make sure that you rename the column in every stored procedure, view, UDF, foreign key, etc, that uses that column in all databases...

What have you tried? 

Now, THAT's what I'm talkin' 'bout

Might also find it useful to put your "Numbers" or "Tally" table there along with an auxiliary date table... make sure you keep the code to build them safe for when...

Micheal Valentine Jones has a faster way but this is an easy way...

Step 1.  Create a permanent Tally table... (it has many, many uses)

--===== Create and populate the...

Heh.... agreed... poor ol' Adam already admitted that the whacko that designed this headed for the hills a long time ago... Who would do this?  I can (possibly) understand needing...

That's a great suggestion... guaranteed to not duplicate between tables and no trigger overhead.

That's a cool function... change the 36 to 27 and drop the 1-9 from the string and I think it'll work for the 0, A-Z range...

Like I said, keep the identity column and add a calculated column.  Takes care of new rows, old rows, etc...   Or, you...