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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Database & SysAdmin
  3. Database
  4. More on DataSets

More on DataSets

Scheduled Pinned Locked Moved Database
csshelpquestion
2 Posts 2 Posters 0 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.
  • N Offline
    N Offline
    normanordas
    wrote on last edited by
    #1

    1. Are there any considerations when to use untyped and typed datasets? I find typed-datasets more useful and less error prone in typo since you can call the members exactly by the name itself besides the fact that it adds some useful methods not present in its counterpart. 2. What condition should stop me from using typed-datasets? Are there limitations? 3. Does datasets supports concurrency..i.e. move the record pointer forward, backward, BOF and EOF? How about bookmarks?

    M 1 Reply Last reply
    0
    • N normanordas

      1. Are there any considerations when to use untyped and typed datasets? I find typed-datasets more useful and less error prone in typo since you can call the members exactly by the name itself besides the fact that it adds some useful methods not present in its counterpart. 2. What condition should stop me from using typed-datasets? Are there limitations? 3. Does datasets supports concurrency..i.e. move the record pointer forward, backward, BOF and EOF? How about bookmarks?

      M Offline
      M Offline
      Mike Dimmick
      wrote on last edited by
      #2

      I'm not sure about #1 and #2, but about #3 I'm certain: a DataSet is a disconnected data store. It doesn't have any concept of the 'current record', there is no record pointer, and no persistent connection to the database is maintained. Until you use Fill a second time, the DataSet contains only the data you originally fetched and your local modifications. Any local modifications are only replicated back to the server when you call Update on an appropriate data adapter object. Stability. What an interesting concept. -- Chris Maunder

      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