^^^ Bert echoes my thoughts exactly.
Don't I always, lol.
@Steven,
I don't know. I think there are issues now that could be resolved, and the PM will have issues and AC (the program) will become the step child.
I read on here once that Jon makes sure he reads every line of code. That all code is approved by him. I am not sure if that is a good thing or a bad thing. But, it certainly must take time.
One thing I have always noticed is that when updates comes out, then tend to fix bugs or add small features here and there. But, you rarely see an update or upgrade completely revamp a part of the program like the vaccine registry (thank God I have VIPER), or the letter writer or script writer. They just stay the same.
Another opinion I will throw out there that would help with support is more support on the website: User guides, FAQ, Knowledgebase, forums. It really only has the forums. I think if it weren't for the forums, many users would really become frustrated.
There is another thread going on about backing up and practicing restoring which has alluded to three different ways: Using your backup, using sync and simply moving SQL databases the correct way. Nothing against using sync, but it is not the way to move a program and neither is using a backup. Once the program went SQL, the technique for moving the program from one computer to another was made more difficult by a factor of 10. If I had to do it, I would simply move the databases. But, this information should be on the website. It should be part of what is termed "best practice."
And, I am sorry. A user-driven wiki is not a user guide or knowledgebase.
Just my opinion.
