Yes, the "D" indicates "debug". Try just copying that file over from your old computer. It doesn't need to be registered.

I'm a C++ buffoon.
 
Does that make me a bad person?

I'll try copying the .dll in question. I just tried recompiling it on my old computer as a release version and it's not working. Why, is beyond me, lol! The program takes a directory path as an argument. If there is no such directory, it exits with an error. For some reason, when I compile it as a release version, it's exiting with that error (even though I'm giving it a perfectly valid argument). But if I compile it as a debug version again, it works fine. Yet both are compiled from exactly the same code. Bleh!

bapu
I'm a C++ buffoon.
 
Does that make me a bad person?

Don't worry, you're in good company 

Are your invoicing needs so strange that an MS Access program can't handle it?
 
I'm not trying to be snarky sharke but putzing around with C++ to interface with Outlook to create invoices seems just like the thing that Access can do with even less programming skills.
 
Seems like you're trying to use a nuclear war head to drive in a common dry wall nail when a hammer will do.

And mind you I do know the adage "if it works...."

bapu
Are your invoicing needs so strange that an MS Access program can't handle it?
 
I'm not trying to be snarky sharke but putzing around with C++ to interface with Outlook to create invoices seems just like the thing that Access can do with even less programming skills.
 
Seems like you're trying to use a nuclear war head to drive in a common dry wall nail when a hammer will do.

It's not as nearly as sophisticated as it sounds, it just parses a bunch of tab delimited files which contain exported Google calendar data (which has been synced from Outlook), turns it into a linked list of linked lists and then produces a pretty colored table (in the command window mind you) which summarizes what everyone owes. I then use this table to create the invoices in Quickbooks. It just basically saves me a bunch of time which would otherwise be spent manually counting what each client owes (because each client's jobs may be spread over multiple employee's calendars). It's the kind of thing which could be done in 30 lines in Python, but I ended up writing it in C++ as a fun little exercise. I don't really have the time or inclination to brush up on any other languages at the minute, especially when this little bugger works so well. 

Well for any interested geeks, it turns out the reason why my release build wasn't working was because the char set for the release build was set to Unicode, whereas it should have been set to 'none.' The stupid thing is I probably happened upon exactly the same issue when I was trying to compile it years ago. Stupid non-photographic memory. 

Well now you know why the Chinese weren't interested in ripping you off.

LOL!