the original error is on the creator of the column in the first place

Allow for something, and sooner or later someone smart will do it. No matter if intentionally or...

Okay, hardcoded percentage. But what about

SET NOCOUNT ON

CREATE TABLE #Trimmean

(

 col1 INTEGER NOT NULL PRIMARY KEY

)

INSERT INTO #Trimmean (col1) VALUES(1)

INSERT INTO #Trimmean (col1) VALUES(12)

INSERT INTO #Trimmean (col1) VALUES(32)

INSERT INTO #Trimmean...

Hm, reread the Excel help. Yes, apparently I missed the percentage parameter. That's interesting. I think, I'll have a play with it this evening.

Forget it!

Obviously I can say that, but it doesn't mean what I wanted to say

I'll stick to nice, I guess.

Your UDF is a bummer!

Can I say that?

One might think, that when SQL Server doesn't like, why did it let the table obviously get created at all? Isn't that the original error here?

Yes, once I found the German translation, it was pretty clear.

Curious how the results are skewed, when you compare who gets the most money and who does the most work....

Hey, I can always blame it on the language barrier. That's a huge advantage at times  Here's the revamped version:

Your UDF is really nice!

Aah, found the translation to the German Excel function. This might look a little bit ugly, but see if it helps:

SET NOCOUNT ON

CREATE TABLE #Trimmean

(

 col1 INTEGER NOT NULL PRIMARY KEY

)

INSERT...

Trimmean

What should this function do? Do you mind giving some more information on what you want to do?

Just another thought:

Have you used sp_spaceused @updateusage = true or sp_updatestats yet?

No, there is no built-in date. I think there are third-party tools that can do this. The crdate is indeed the creation date and it will also serve your purpose...

It's me who is thankful! Your UDF is really cute. Good to see your blog is back online again. I tried this morning (European time) and got some strange runtime...

When one looks at all your questions today, one might be inclined to say, it's a good idea for you to get a copy of Ken Henderson's Guru's Guide to...

Since your question is not directly related to SQL Server, but rather general Windows programming, you are likely to find excellent information on MSDN or TechNet. Have you searched there...