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. Visual Basic
  4. Save all User entered Data

Save all User entered Data

Scheduled Pinned Locked Moved Visual Basic
databaseoraclesysadminquestionannouncement
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.
  • L Offline
    L Offline
    Lost User
    wrote on last edited by
    #1

    I have a data entry entry screen. Here users are entering Checks details in batches. Each batch is having about 200 checks. User wants to save each row after finishing the row. I did by using XMLDom. Which is calling another page? It is perfectly submitting the values to the database? But it is slow and putting lot of load on the front end and increasing heavy network traffic in a 50 people environment. Is there any better way to Insert, Update, delete the rows. I am using asp, Oracle with IE 6.0

    V 1 Reply Last reply
    0
    • L Lost User

      I have a data entry entry screen. Here users are entering Checks details in batches. Each batch is having about 200 checks. User wants to save each row after finishing the row. I did by using XMLDom. Which is calling another page? It is perfectly submitting the values to the database? But it is slow and putting lot of load on the front end and increasing heavy network traffic in a 50 people environment. Is there any better way to Insert, Update, delete the rows. I am using asp, Oracle with IE 6.0

      V Offline
      V Offline
      vasuonline
      wrote on last edited by
      #2

      By saying Front end , do you mean that browser? If so, make sure that the asp page doing database update is returning only S(uccess)/F(ailure) message and then updating the DOM? If that is the case, it shouldn't put any load on front end because the page does not get refreshed. Web-server load (so with N/W load unless it demands upgrade) is ok for 50 users because 50 users can not be 50 concurrent connections, in web environment. cheers vasu

      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