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. datasets disappear from designer

datasets disappear from designer

Scheduled Pinned Locked Moved Visual Basic
databasexmlhelptutorialannouncement
1 Posts 1 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.
  • J Offline
    J Offline
    JimWDurbin
    wrote on last edited by
    #1

    We have had multiple occurances of datasets disappering from the designer. We cannot be specific about the circumstances since we simply do not know when this will occur or under what conditions. The .xsd and associated .vb files are still located in the source directory. The .vbproj file has references to both but is missing the following tagged lines (as an example). Restoring the tagged lines allows the code to compile correctly, but the data sets still do not show up in the designer. The implication is that we can't select the dataset and look at or modify the schema. Here is a snippet from the .vbproj with the missing lines tagged by >>> >> DependentUpon = "LabNfonts.xsd" SubType = "code" >>> BuildAction = "Compile" >>> DesignTime = "True" >>> AutoGen = "True" /> >> Generator = "MSDataSetGenerator" >>> LastGenOutput = "LabNfonts.xsd" /> We are using a single data adapter and reconfiguring it to generate each data set. At execution time, the dataAdapter select, insert, delete, and update comman text is dynamically altered. The only other way we have found to get the datasets back is to completely delete the dataset and all references to it in the MS generated code, then reconfigure the dataAdaper and regenerate the the dataset. This is a huge waste of time, and I believe there must be s simple solution for prevention and cure of the problem. Any insight would be greatly appreciated. Thanks.

    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