Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>1.) I would recommend using the BackgroundWorker instead of separate threads like this. Your worker will catch exceptions and pass them along as a parameter to the complete handler.</p> <p>2.) I would use ShowDialog() instead of Show() when displaying the second form, this will block the DoRun() at that method call and exceptions should then be caught by your surrounding try / catch (or the BackgroundWorker if you're using that instead). </p> <p>I think the problem comes that since you're calling Show() you're essentially dispatching that call onto the Invoker, which ends up being queued in the UI thread. So when an exception happens there is nothing higher up the callstack to catch it. I believe calling ShowDialog() will fix this (and also allow you to drop that nasty for loop).</p> <p>Something like this:</p> <pre><code>public partial class Form1 : Form { public Form1() { InitializeComponent(); } private void button1_Click(object sender, EventArgs e) { // NOTE: I forget the event / method names, these are probably a little wrong. BackgroundWorker worker = new BackgroundWorker(); worker.DoWork += (o, e) =&gt; { Form2 f = new Form2(); e.Result = f.ShowDialog(); }; worker.DoWorkComplete += (o, e) =&gt; { if(e.Error != null) MessageBox.Show(string.Format("Caught Error: {0}", ex.Message)); // else success! // use e.Result to figure out the dialog closed result. }; worker.DoWorkAsync(); } } </code></pre> <p>Actually, now that I think about it, it's sort of weird to be opening a dialog from a background thread but I think this will still work.</p>
    singulars
    1. This table or related slice is empty.
    1. POPreventing Unhandled Exception Dialog Appearing
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USjustin.m.chase
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPreventing Unhandled Exception Dialog Appearing
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes, opening a dialog from a thread other than the main thread for the application is not only weird, but dangerous. It's just like changing the UI from a non-UI thread. It can and will blow up on you at run-time. If you need to show a dialog based on something in another thread, you need to send an event from that thread back to the UI thread, which can then show the dialog.
      singulars
      1. PO
      1. USjasonh
    2. COWhen I say "send an event back to the UI thread" I mean that the worker thread should *somehow* cause a form or control on the UI thread's Invoke or BeginInvoke method to be called. Exactly how you want to do this (I use an event and then the Form has a method that checks InvokeRequired before directly calling the method that shows the dialog or calling Invoke/BeginInvoke on that method) is up to you.
      singulars
      1. PO
      1. USjasonh
    3. COOutstanding! Thanks Justin
      singulars
      1. PO
      1. USrc1
 

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