…by me. We went live on Monday. I spent all day looking through the data. Found a few things that didn’t get imported, a few things that didn’t come in right, etc. I’d email our rep (Laurie Goodrich) and our person who did the data conversion (Rob) and the problem would be fixed within less than 30 minutes. I THOUGHT the billing addresses for our customers that have multiple sites should have been imported, but thankfully, Rob knew better. If he had done what I *thought* we needed we’d have a lot of duplicated records in our new, nice software. That would have been a travesty!

I thought there were a lot of extra clicks just to get to the system password so I emailed support asking that it be easier to get to. Within 10 minutes or so, I had an email telling me how to get to it faster than I was doing it. Screen shots and all. Then a minute or so after that, I got an email from a developer with a screen shot showing how it will be easier to get to on the next update. Can’t ask for faster service than that!

One of my favorite things is that there are so many ways to do one thing. At first, it seems to complicate things. But in the long run, it’s really nice because you can use the software in a way that works best for you.

Automatic credit card processing is going to take a lot of work over the weekend. Alarms for windows didn’t delete the information when you took someone off of auto, so we had a lot of bad ones imported. As far as I can tell, there was no way around that. It seems that it was still better to bring it all in so I didn’t have add all the credit card numbers manually. I just have to delete the entries that I don’t need. Can you believe that Alarms for Windows stored all that bank and credit card data raw in the database? Sure glad we’re getting away from that software.

I just really can’t think of any complaints about the software or the transition. I’ve been worried about it for months, just not knowing how well the data could come in. There was so much trash data in the old Top Speed database. Alarms for windows would widow records all over the place.

I don’t think I could have asked for a better conversion experience!! Thanks Laurie and Rob!

I looked this place up online and couldn’t believe the negative reviews. It really surprised me.
While were in on Marco Island, we wanted a good place to eat and tried Joey’s out. I was very impressed! The garlic bread knots are to die for. They were hot, soft and gloriously garlicy.Yum! My father in law even liked the lasagna, which is surprising since usually lasagna doesn’t have enough meat for him.
If you’re ever in Marco Island, Florida give Joey’s a try.

More info on Joey’s Pizza and Pasta House

This is something I’ve been wanting to write for a long time. I won’t get it all out of my head tonight, but thought I should start.
We’ve been using Alarms for Windows for billing for almost 10 years now. It has some great ideas, but sadly not much of it is planned out very well (don’t even get me started on the database design!). After going to the user conference for SedonaOffice, I know where this product (Alarms for Windows) struggles and that’s with it’s developer. It’s a one man show and he does NOT like to hear that something doesn’t work or that it wasn’t executed very well. Anytime you mention something doesn’t work, it’s always your fault for using the program incorrectly. And, you’re told it doesn’t happen to anyone else, everyone else uses the program with no problems. Yeah, right.
I went to the SedonaOffice user conference and it was a completely different world. The co-founders were there and very much cared about the product and where it could go. Imagine this…they WANTED our feedback on how to make it better. They didn’t take it as personal criticism. The SedonaOffice community is very open in sharing ideas. I don’t know how many times the co-founders (Michael Marks & Don Faybrick) said, “Hey, that’s a good idea. Let me write it down and talk to the developers”. Such a nice change.
I learned something else, too! I met a President/CEO from an alarm company in Maryland that just switched to SedonaOffice last September. Guess what software they migrated from? Alarms for Windows! They used the software for 12 years and had MANY similar stories that we did. Turns out we were not the only ones that had a miserable failing migration to the Alarms for Windows SQL (we were told we were). We also didn’t have the largest set of data, they were told they did as well. I’m also not the only person who has recieved nasty, rude emails from the developer of Alarms for Windows. I feel better now knowing I wasn’t the only one treated that way.