The alternative is to write a query instead an "on the fly" ad hoc mess.

So, how do...

Are you sure that would be true in this case? A trip to the disk should always turn out to be slower than a relatively simple trig calculation...

Not if you're using a constant for a multiplier on latitude...  if you are not using a Cosine based formula, it does not take the curvature of the Earth into...

Yeah... especially since I might use my pickup to pull a santion out of the building just to get their attention

Yep... I forgot those... the security concerns, that is.  If you are using stored procs, the users don't need huge privs to use the program as they would with embedded...

I agree... there's still some info missing...

Brian, are you simply saying that you want to be able to update any row and insert new rows from the app?

Or are you...

If it's the Primary Key, then you may be (will be) destroying referential integrity for other data in other tables.  If it's the Primary Key and you don't have referential integrity,...

I'd never use @@Identity because it is not scope sensitive and, in the presence of triggers, will surely return an incorrect value.  Always use SCOPE_IDENTITY for such a thing.

Yes, it is possible to modify the number by first doing a SET IDENTITY INSERT... here's the syntax from Books Online...

SET IDENTITY_INSERT [ database. [ owner. ] ] { table...

Actually, there is one method that's a few milliseconds faster over a million or so rows...

SELECT CAST(CAST(datecolumn-.5) AS INT) AS DATETIME)

As usual, please don't take my word for...

Felix...

You may want to post some of those custom functions you're talking about... you'd be surprised at how some of them can be speeded up or maybe even eliminated with...

And, you still need to determine.... is null a date way back in the past or a date in the future?

The destination table has a ROWID field which cannot be an identity key, ...

Why the heck not?