Post reply

n: Insert Error: Column name or number of supplied values does not match table definition

  • October 24, 2005 at 4:22 am

    #188135

    I suddenly started getting the above error.

    I tried to implement a merge replication, which failed due to the fact that I missed a couple of related articles, and since then some stored procedures on the publisher have started failing with this error. I haven't explicitly changed the stored procedure or the table definition so now I'm very confused...

    Anyone know what might be wrong?

    TIA,

    Phil

  • October 24, 2005 at 4:45 am

    #599438

    Of course we all know that merge replication adds a guid column to replicated tables.

    I didn't realise it would mess up existing insert statements though - shouldn't it just use the default value (also automatically applied by merge replication) if no value is specified?

    Feeling silly,

    Phil

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply