Make sure that the logon account for the SQLServerAgent on the Publisher has access to the subscriber database.

Mark

Try this:

Select sum(CS_SHPCHG) As FreightCost

  From CS_Package p,

       (

         Select distinct B.PackingSlipID from CustInvoiceTrans A

           Inner Join CustPackingSlipTrans B ON A.InventTransID=B.InventTransID

           And A.ItemID=B.ItemID And A.SalesID=B.SalesID

           Where A.InvoiceID like...

You will get that error if there is no '-' in TYPE.  You can get around that by doing a check first.

SELECT

  CASE CHARINDEX('-',type)

    WHEN 0 THEN ''

   ...

Try

SELECT RIGHT(Type,CHARINDEX('-',REVERSE(Type))-1)

Mark

From Frank Kalis' post on July 20:

"D and E are used in Fortran to represent FLOATs in scientific notation. SQL Server internally uses C routines for ISNUMERIC that follow these...

In Enterprise Manager, Expand the replication folder and publications folder on the publisher.  Right click on the publication and select properties.  On the Subscription Options tab uncheck the "allow Anonymous Subscriptions"...

How did you remove replication?

sp_removedbreplication <dbname> should remove all of the replication objects from the database.

Mark

Try running sp_removedbreplication 'dbname' on the publisher.

That should remove all replication objects from the publication database.

Mark 

Sounds strange.  Does that same column replicate from the publisher to the subscriber successfully?

I assume you have checked the column filters to make sure that column is not being filtered accidentally. ...

Check the Server setting properties on the publishing and subscribing servers and make sure the "Allow triggers to fired that fire other triggers (Nested triggers)" is enabled.

We had a case...

Farrel,

You have a typo in your example of my query.  Try the query below.  It will give the same results as the *= and your query.

SELECT t1.id1, t1.data1, t2.data2

FROM(...

Are there any triggers on that table other than the replication triggers?

Mark

The reason it returned the results it did was because (again using your first example) the optimizer applied the "WHERE t2.data=2" and  "WHERE t1.data=5" before doing the join.  As in my previous message the syntax below...

Using your first sample data:

SELECT t2.data,t2.id, t1.data

from (SELECT id, data FROM table2 WHERE data = 2) t2 left outer join

     (SELECT id, data FROM table1 WHERE data = 5) t1...

SELECT     t2.data,t2.id,t1.data

from table2 t2 left outer join table1 t1

    on t1.id=t2.id

where t2.data=2 and t1.data=5