Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. LINQ
  4. SubmitChanges doesn't work

SubmitChanges doesn't work

Scheduled Pinned Locked Moved LINQ
csharpdatabasevisual-studiodebuggingtutorial
2 Posts 2 Posters 2 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    threemp3
    wrote on last edited by
    #1

    Hi I've got a DBML file with tables and when I use InsertOnSubmit() then call SubmitChanges() it'll return a correct object (with new values), but when I exit from debugging, it doesn't store the changes in the DB. I read somewhere that VS.Net copies the DB everytime you debug by default, but I couldn't find out how to stop that. Can anyone please provide me with details on how to do that? Thanks

    S 1 Reply Last reply
    0
    • T threemp3

      Hi I've got a DBML file with tables and when I use InsertOnSubmit() then call SubmitChanges() it'll return a correct object (with new values), but when I exit from debugging, it doesn't store the changes in the DB. I read somewhere that VS.Net copies the DB everytime you debug by default, but I couldn't find out how to stop that. Can anyone please provide me with details on how to do that? Thanks

      S Offline
      S Offline
      SuperJB
      wrote on last edited by
      #2

      Hi... just starting to work with LINQ (better late than never)... I'm having the same conflict with SubmitChanges() method... DOESN'T WORK! I've seen in forums that the problem is the table having a PrimaryKey defined... not the case! Did you ever get this to work? SuperJB

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups