That's what he knows.

This may happen if the server is re-booted and the windows performance counter service is running. Turn off the windows perfomance counters, then re-start SQL Server, and then start the...

Check the SQL Server Network Utility and make certain that Force Protocol Encryption is UNCHECKED.

 select Facility,District,Division,EntryType,Series,Totals, (Cast(cast(Totals as numeric(6,4))/(Select cast(Sum(Totals) as numeric(6,4)) from PunchTrend b) as numeric (5,4)) * 100.000) as Percentage

from PunchTrend a

Order by Facility,District,Division,EntryType,Series

Check out this reference:

http://windowsitpro.com/articles/print.cfm?articleid=22264

You may want to check the users defined in the MODEL database as well, just in the event the windows group is defined as users there.

Perhaps the client machine will need to set up an alias for the server machine in the client's SQL Server Client Network Utility.

Here is another link which may be helpful. It uses DTS ActiveX task to script other DTS packages:

http://www.nigelrivett.net/ScriptDTSProperties.html

Here is a link to scriptpkg.exe usage:

http://support.microsoft.com/default.aspx?scid=kb;en-us;239454

Use <database to query>

GO

Select * from INFORMATION_SCHEMA.VIEWS where

patindex('%<table to identify>%', view_definition) > 0

CREATE procedure sp_runpkg @t varchar(100)

as

declare @s-2 nvarchar(200)

set @s-2 = 'master.dbo.xp_cmdshell ''dtsrun /S<YourServerName> /E /N' +  @t  + ''''

exec master..sp_executesql @s-2

GO

I believe I solved my own problem. Thus,

ALTER TABLE MYTABLE

Add MemberSeqNbr int NULL

update mytable set memberseqnbr =  (select count(*) + 1 from mytable m1 where mytable.membernbr = m1.membernbr and mytable.startdate...

MemberNumber and Startdate

Collation compatibility may be an issue.  Make sure you have the compatibility you want by checking the appropriate box in the linked server --> Properties -->Server Options applet tab.

Glückwünsche! Eine wohlverdiente Ehre.