Jeff, Just making sure, some could take it that I was.  I didn't test throwing in the collate in the select on the case insensitive server to see if that...

Jeff, I wasn't suggesting that server collation be changed, just that it be checked.  We have several PeopleSoft servers and they are set to Latin1_General_BIN, so when I started looking...

Try this, but it may not be the most efficent way of doing it:

DECLARE @CoName varchar(30)

SET @CoName = 'Not Assigned'

---

SELECT SUM(A.Invoice), A.InvoiceDate,

CASE WHEN C.CompanyName IS NULL THEN 'Not...

Steve, To build on what you started, the data field in your 'generic table' could also be a SQL VARIANT, then you would only need one column for the data...

I don't think that has anything to do with it.  What is the collation of your server?  I think you will find it is set to a case insensitive collation.

You could update the column in the order header with the count of line items using a trigger on the detail table.  As the trigger is updating a single row...

Case insensitive collation, ran it on one of our servers with a case insensitve collation and it hit on the 'a'.

Possibly also Accent Insensitive on your collation.

Here is my guess, you have a case insensitive collation, therefore 'a' = 'A'.  I ran you select on my system and it returns a 0, and I use a...

Are you trying to buy it directly from Microsoft?  I went to Microsoft site and it looks like I could purchase what you are looking for at this site:

http://www.microsoft.com/products/info/product.aspx?view=22&pcid=a0cccd9a-c37e-4d82-9329-8d14c1cbd7ae&crumb=catpage&catid=cd1daedd-9465-4aef-a7bf-8f5cf09a4dc0

Give this a try, couldn't hurt:

select

    Type,

    Version_Name,

    FISCALYEAR,

    M1,

    M2,

    M3,

    M4,

    M5,

    M6,

    M7,

    M8,

    M9,

    M10,

    M11,

    M12

from (

IF EXISTS (SELECT

               AG.GroupMeat_Name,

               GLAGData.AccountGroup_ID

           FROM

               Export_AccountGroup AS AG

              ...

Off hand, no, but that isn't what I thought you were asking for either in your original post.  I'll have to look at this a little more.

Have you also checked the DTC configuration on Server B?  We had similiar issues between our servers running PeopleSoft, and we had to modify the DTC settings on both servers...

Check BOL, DBCC CHECKIDENT.

Looks like this:

DBCC CHECKIDENT('DAWNTEST', RESEED, 500000)

You can create UDT's in SQL Server 2000, sp_addtype in BOL for SQL 2000 shows how.  Used this a few times at a previous employer.