We do formal testing approach, however typically the tests only test what has been changed not what those changes might effect..however this is slowly changing with more support/qa personnel and...

Ok so im an idiot but i do hope it helps anyone else out there..

I figured it out for at least my problem anyway and is as follows.

The problem is...

Wow, ive never had probs with my razr like that which have been discussed here...gotta wonder if the one sold in AUS is manufactured in the same place as the...

You may not need to use a different card, i have found (as stupid as it seems) taking the card out of the PocketPC, doing a soft resest and putting...

Have the solutionms you suggested worked??

1)where is the datbaase being opened from? PDA or Card?? if its from a card, maybe taking out the card and putting it back in...

RAZR V3, if synching is important to you though dont get this phone, but i find the clarity of voice hands free and coverage very good...

ROKR from motorola is cool...

Thanks for confirming my suspicions with how it works..i think i will try relocating the temp db if i can do that to the SD card that will work, most...

Thanks for the reply

actually we store the db on a SD card and the db is actually sitting pretty at about 200mb's now.. we have to partition the db's which...

Essentially you need to script out your views and SP's (take care that if there are dependancies you sort them out)

Save the script into a folder in REPLDATA

open your publication...

Ok we found where the sp is its in master db..the initial error is still valid

yep,

are you using a pocket device or anonymous publication?, a snapshot (or a task in the snapshot process) may clear out these tables hence them dissappearing..

fun and games

Further to this ,

sp_msGetReplnick seems to be involved with this and returns null, which seems to be the cause of the error, im trying to find out where this sp...

Do the duplication happen on the merge? or is it the actual trigger causing the duplication??

Regards

Adam

Follow up to this from me,

we actually dont replicate the views anymore, rather we script the views and run them as a post replication/snapshot script..this works well.

I can elaborate if...

Just thought id throw my 2cents into this as well, just started recieving this error after applying the latest batch of updates from MS (Novmeber 2005 updates)

Windows server 2003...