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. Client - Server

Client - Server

Scheduled Pinned Locked Moved Database
sysadminhelpcsharpcss
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.
  • A Offline
    A Offline
    alav
    wrote on last edited by
    #1

    How to implement a database server , in client-server local network,(we are using visual basic 6.0 and sqlserver 2000). The problem is ,if the connection is not available than we can't get the master datas from the server. If it is .net it is no problem. because it support connection less database. But if we use visual basic 6.0 , what is the way to persist the data from server after terminate the connection. Please can anybody help Thanks in Advance

    P 1 Reply Last reply
    0
    • A alav

      How to implement a database server , in client-server local network,(we are using visual basic 6.0 and sqlserver 2000). The problem is ,if the connection is not available than we can't get the master datas from the server. If it is .net it is no problem. because it support connection less database. But if we use visual basic 6.0 , what is the way to persist the data from server after terminate the connection. Please can anybody help Thanks in Advance

      P Offline
      P Offline
      Pete OHanlon
      wrote on last edited by
      #2

      I think you have a bit of a misunderstanding of what connectionless means. While your program is running, data can be persisted into memory. If the application stops and restarts, then it needs to get the data again (this is simplified, and doesn't address out of process databases). While DataSets are designed to be disconnected, it does not follow that .NET is connectionless. If I open a DataReader and don't close it, then we have a connection. At some point you will need to get the data out of the database and this is where your problem kicks in. In both VB6 and .NET, if you can't get to the database because a connection isn't present then you are stuck. If you want to store the information in memory, and you can get to it, then you can use exactly the same mechanism for VB6 as for .NET, i.e. you read the data into something that exists for a period of time. It could be that you store a recordset in memory, but however you do it, at some point you will need to persist these changes back into the database server. You will need to consider the implications of stale data and optimistic/pessimistic saves.

      Deja View - the feeling that you've seen this post before.

      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