Databases
StackOverflow2013
Usersdbo
USDragonsRightWing
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USDragonsRightWing
    primarykey
    data
    text
    plurals
    1. PO
      singulars
      1. PTAnswer
    1. POUAC gives me fits!
      singulars
      1. PTQuestion
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COThanks, Pavel. It looks as if I'm going to have to use a single EventSource, then use some alternate means of further identifying the "Inner Source". Again, the problem is that the application is not actually installed on the machine where the Event entries need to be written. You have gotten me interested in WiX, however - I have not looked into it before now.
      singulars
      1. PO
      1. USDragonsRightWing
    2. CO1) sorry about the hard-to-read formatting on the last reply ... 2) What is the purpose of EventLog.CreateEventSource - if not to Create Event Sources? In our situation, we may be logging to a physical host on which the application has not been installed, but is being run as a remote application: we want the Events to be written on the client, not the application server. I am not using the auto-create, but specifically testing for, then (if needed) explicitely creating, the EventSource.
      singulars
      1. PO
      1. USDragonsRightWing
    3. COIn the Solution Explorer, right-click the default project: choose Add>New Item In the dialog, select the Installer Class template, name it A new class is added - after the call to InitializeCompnent(), add this code: if (!EventLog.SourceExists("MySource") EventLog.CreateEventSource("MySource", "Application"); Add a Setup Project & add Primary Output Right-click on the Setup project, select View>CustomActions Right-Click the Install folder, choose Add Custom Action Select Application Folder, then Primary Output - click OK. Save & Build - the code you added runs at setup
      singulars
      1. PO
      1. USDragonsRightWing
 

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