puzzlepiece87

@this (Nicely done and I am glad I was headed in the right direction. Didn't pick up that there was a separate OrderLineItems table, I thought that OrderLineItems was just a field in the RefundLineItems table and that's why Mat is talking about them not being easy to link at the line level. Still waiting for more details to emerge but nice take on the problem.)

7 for the original record, 7 for the matching record, 1 to put out results

That beats my record, my record is currently 15 for researching duplicate medical claims.

I'm going to stop flailing haha, I apologize for not understanding your current situation well enough to help even though you described it in medium detail already

You didn't say this explicitly but I'm assuming from what you said that RefundLineItems has OrderID in it and you are joining on that

That's probably hopelessly off base but maybe if you show us your existing join criteria that might help? You probably already stated them and I didn't understand.

bye, sorry I couldn't help

or no?

So RefundLineItems has OrderID in it?

Oh oh oh okay

I'm goodish at SQL and feel optimistic about my chances to help once I understand what you're trying to accomplish.

Sorry for all the silly questions

Or maybe the correct amount is order $ - sum of refund $?

Which is the correct amount? The latest amount? The sum/total?

Are you trying to find refunds for a specific order-line and then find out what order that order-line corresponds to?

Are you trying to find if an order has any refunds in true/false format?

Dumb question, feel free to ignore: what specifically are you trying to find?

> The row limit is well known and documented. Calling the row limit a "glitch" is like saying "Ford Mustang glitch prevents cross-Atlantic road trip."

@Vogel612 Ah interesting, a CR games room.

And the UK has been competing with the US in being maximally 2020 so this is very on brand for them

Everyone wants the good stuff right now for free

Exactly

I'm just laughing at the consequences experienced for such a bad decision

Nope, happens way too often to be surprised

That seems like something that would make this group laugh and roll their eyes at the same time :P

Did you all get some laughs in out of hearing that the UK's screwed up coronavirus case counts came from using Excel as a database? xD

@MathieuGuindon Just signed in to see if I had any follow-up comments on a self-answered C# question and I immediately saw you helping people with VBA. Thanks for continuing to be such a wonderful presence in the community :)

@M.Doerner I looked into these over the weekend and may use them. Thank you!

I will also, of course, consider a more typical WPF architecture, but I'm first trying to make sure I understand how Tasks and Async/Await apply to the existing architecture.

@M.Doerner Thanks for all your feedback! Yes, Landing is a window that is closed after the user selects an initial option and is re-opened if they cancel their initial selection. I'm going to look into what you told me about explicit shutdown and see if that would be the best solution as far as allowing tasks to continue to run asynchronously without waiting on them.

@MathieuGuindon Oof, sorry you're only just now getting to WFH and having to work two jobs :(

@M.Doerner I have to wait for a task to finish because otherwise the program finishes executing and exits before it returns. I invoke them via Task.Run(() => )

Read your thread, misspoke in calling my program a console app because I don't use a console. What I actually meant is that all the work is being done largely independently of any kind of graphical interaction.

(In between juggling my other requests)

Right now I'm trying to follow up on what you two told me today by finding the very first command after the GUI is done (except the progress bar) and Tasking out from there instead.

I'll get it eventually.

Like misunderstanding the basics of offloading or something.

@HackSlash I'm almost certainly doing something really dumb.

I can't maintain it as a sole developer, too little use so far

I just finished taking command line stuff out actually

The graphics are just for user configuration and progress display

Seemed like it was an appropriate fit because most of the stuff my program does is CPU-bound text file editing

I learned it from VBA, mostly.

Manually controlling window instances from the code rather than letting WPF guide from one window to the next.

I think Mat favors the same approach himself.

@HackSlash xD

@HackSlash I'm using WPF with a Console-like starting point.

Because there were no other steps left in Main() to execute

In my memory, when I kicked off the ParallelFileProcessing without awaiting, it gave control back to the caller, Main() basically, and the program ended.