This is a great start! Please continue to flesh it out, and adding some stuff around the SQL Server and how to best maintain, etc. as well would be great.
Thanks for your comments, Mark! I will add your suggestions to the list of topics to add to the docs for the next release.
In the Note on page 21 on importing user data, can we add that there needs to be some modification to the file from the archive before you can import it again like what is in the Help File or mention "For more details see the Pharos help File."
In the archive section can we make a BIG note that the only data that can be re-imported is user data, nothing else can if you do it accidentally.
In the archive section can we make a note to make a backup of the database first, in case someone changed their mind on removing the data.
Thanks Jeff. Good timing! I'll add your suggestions to Uniprint 9.1.
It would also be nice if the Administrator itself had a huge warning about archiving data. It seems that at least once a quarter a customer is archiving something for one reason or another and then wonders what happened when the reports are off. They just do not associate archived devices, computers, or users, with archived transactions and therefore altered reporting data.
Thanks for the suggestion, Steven. I'll add it to my list of things to do for 9.1 release.
Retrieving data ...