Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POPrompt Dialog in Windows Forms
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSean Worle
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy is this not a good idea? What are the possible "compatibility" and "ability to upgrade" problems? I'll agree that "stylistically" speaking, most C# programmers would prefer not to use classes from a namespace called `VisualBasic`, but that's only in their head. There's no reality to that feeling. It would just as well be called the `Microsoft.MakeMyLifeEasierWithAlreadyImplementedMethods` namespace.
      singulars
      1. PO
      1. USCody Gray
    2. COIn general, the Microsoft.VisualBasic package is meant to simplify upgrading code from VB 6 only. Microsoft keeps threatening to permanently sunset VB (though this will probably never actually happen), so future support for this namespace is not guaranteed. Additionally, one of the advantages to .Net is supposed to be portability - the same code will run on any platform that has the .Net framework installed. Microsoft.VisualBasic, however, is not guaranteed to be available on any other platform (including, for what it's worth, .Net mobile, where it is not available at all).
      singulars
      1. PO
      1. USSean Worle
    3. CO**Incorrect.** That's the `Microsoft.VisualBasic.Compatibility` sub-namespace, not the entire thing. Lots of "core" functionality is included in the `Microsoft.VisualBasic` namespace; it isn't going anywhere. Microsoft has threatened to "sunset" VB 6, not VB.NET. They've promised *repeatedly* that it's not going anywhere. Some people still don't seem to have figured out the difference...
      singulars
      1. PO
      1. USCody Gray
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload