MICROS Report Emailer 1

[Moregelen]

I don't know if anyone is interested in this, but I had a sight with no myMicros that wanted daily reports emailed. The solutions I could find were always really convoluted to set up, and if they didn't run, I would have to go in and recreate the report and then manually send it, because it didn't save a copy. It was also quite difficult for customers to edit it themselves, so I whipped this little thing up. If anyone wants to use it, feel free. Requires .NET framework 3.5. Service won't start if you don't define any reports; you can install/stop/start/uninstall the service from the GUI.

https://www.dropbox.com/s/unf60sh9a76eh48/MICROS Report Emailer v1.3 Setup.exe

 

[Moregelen]

I really wish I could edit my posts, because it just kills me when I see grammar errors like 'site', 'sight'... blargh.

 

[Wildbar]

Will check it out. We use the one licensed by Micros, although I can't remember if it cost anything. We do use it a lot though and think its a great addon. I am sure yours will be as well. Kind of amazed they have not rolled something like this into the core 3700 software.

 

[Moregelen]

The one licensed by Micros? Do you mean MyMicros? I've never been able to find one officially support by Micros other than MyMicros.

 

[Wildbar]

Micros Canada made one, or one of there techs did and Micros picked it up. Called Micros ReportMailer. Similar to yours but it also has the option of sending reports at three different times (we use end of day, and of week, and end of month) and it ties into auto sequences so the report printing and send out is automated. I think I still have the setup program if you want to take a look at it.

 

[Moregelen]

Nah. Its ok. I specifically wanted one that didn't tie into the Auto-sequences directly. And, technically, mine can send the emails at any time. The difference being of course that you have to create the auto-sequence step, and then the report template. You can create as many as you want, but each one is going to send a single report per email. A bit of a down-side I guess.
I didn't want to directly tie into the Micro database because my boss gets uneasy when I start screwing around with things that could potentially cause a system to go splodey-boom, however unlikely.