There is an Update trigger, but it just updates the timestamp.

Here is the DDL- (see following post for my insert code)

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_PADDING ON

GO

CREATE TABLE...

The table def is in above post (let me know if you need more). And yes, the incrementing id is done from the trigger if the value comes in...

Something like this perhaps?

DECLARE @inString varchar(50)

SET @inString = '24302331 - IVA a 21% OBS'

print LEFT(@inString, CHARINDEX('-', @inString) - 1)

Yes, on a uniqueidentifier column named 'rowguid'. Default value is newid()

AgeIDsmallint

Hosp_IDvarchar(20)

Age_Unitvarchar(6)null

Activebit ...

Ok, well this works too but isn't much prettier. Still seems like there should be some slick in-line way to do it...

DECLARE @maxNum int

DECLARE @increment smallint

SET @maxNum = (SELECT...

Ugh, what a hassle. I have to do this for about 50 tables, anybody know an easier way?

We figured it out with this tip. "The password is converted to a wide character format (UNICODE) and each byte XOR'd with a constant fixed value of 0xA5". ...

I just thought you had to execute dynamically (with EXEC or sp_executesql) anytime you used a variable in your statement.  I was really disappointed w/ SQL Server regarding this when I moved...

Is the ability to use a variable within a SELECT new to 2005?  Is it limited to specific functions, such as TOP?

You are correct, it is still hardcoded but the...

If I used 0.0, why would the conversion not take place?  Wouldn't it just convert to a dec instead of an int?

It worked, thx!  Is NULLIF new in 2005?

Yuck, but ok, that's kind of what i thought.  FWIW, here's what i came up with, made even uglier by the fact that there may or may not be seconds, milliseconds.

Thanks!

All of the fields used to populate table variable @tblIdFields are from static, application architecture tables.  The application itself is a reporting tool, and accepts no user input (except choices...

I ended up not putting the code in a field, and instead went this route.  Let me know if anyone wants me to post the entire code, but I think...

Very good point, but the code does not actually exist in a persistent table.  I construct the code statements from several fields in 2 different tables, and the code field is...