I don't know if your real query follows the same logic

but the sample query should work as shown below.

using the logic

if

A = 'F' and

...

Oh btw..

If your only aggregate is the count

and you use the subquery posted by Deuce,

then you can get rid of your 'Group by'.

The reason you are having problems is because of the database structure. There should never be duplicate data. The best long term solution is to redesign the datbase structure to...

Does this work at all...

Select *

From Table

Where

(

Soundex('combuterrr') = Soundex(ColumnName) or

ColumName Like '%computer%'

)

Oops.. a little error on the last script.

The way the script was written forces @ID to be defined prior to execution. I think the following code is correct..

Declare

@CommandString...

Just in case you need something more dynamic...

Declare

@CommandString Varchar(1000),

@WhereClause Varchar(1000),

@Surpress int

Set @Surpress = 0

if @Surpress = 1

Set @WhereClause = '' ...

Check The Replinfo field in sysobjects for the object in question. It should be 0 if the object is not replicated

Good Luck

That error usually means the bcp file can not be found.

It appears your subscriber has succesfully connected to your ftp server but the file it's looking for is not...

SQL Server 2000 allows changing articles without dropping replication..

I don't know if that will apply in your situation but it's just a suggestion.

Good Luck

Merge uses a rowguid whose property is specifically set as ROWGUIDCOL ( vs uniqueidentifier ). Other RowGUIDs in the tables should have no affect on it.

I have seen that exact problem with regional settings. Your computer is giving a datetime in a format the sql may not be able to interpret as a datetime.

The floating...

The replication agent should be ran by a job. That job has a schedule.

Right click the Job in EM and choose properties. Click the schedule tab and set the job...

I just read the latter comments about the missing sysmergepubliccations.

You might have to drop the subscription and re-create it. You will also have to re-sync the databases.

Reinitializing the subscriptions will...

That sound like a problem caused by different service packs.

Use Select @@Version on all of your servers and verify the service packs are the same on all servers.

If they are...

You could use your home machine as the publisher. Your host maching would subscribe to the published tables. Any changes made to tables at either end would be synchronized.

(merge replication)

Next...