HAPPY SYSADMIN DAY!!!
I know that you get very little thanks from those who need you the most and I can’t let that happen here at Bozteck!
You are the reason that VENM exists and I am truly thankful for each person who has supported us through the years with license purchases and awesome feedback!
Bozteck is not a large company and we aren’t exactly getting rich by keeping the price so low but it’s so worth it every time that I hear your stories of how Bozteck VENM has saved you time and trouble. (keep ’em coming!)
It makes me feel like I’m really making a difference and I can’t thank you enough for that.
It’s Friday – grab a cold one, put your feet up, and be proud of the difference that you are making.
We’re thinking about adding the ability to lock down certain portions of the application in a password protected “Limited” mode that is very much like the Parental controls in Windows.
The default mode would be full rights. You would set it into “Limited Mode” in the program preferences and set the password there also.
Is this something that you would find useful?
In the early years of VNCScan, all of the data was stored in a Microsoft Access database and the settings were stored in INI files. This worked well but required that I distributed a lot of additional runtime files to access the database(pardon the pun).
In late 2003, I decided to move away from Access in favor of flat XML. To this day, I still debate with myself which was better because each have their issues. The XML file format for data made it possible to ship a smaller product with less dependencies but it severely limited the multi-user capabilities for sharing data.
The XML format is just plain text files. When one console reads the data and then writes a change, there’s a chance that another console that is also reading from that same textual XML file can write back what it thinks is accurate data and overwrite the first consoles changes. It can get messy real fast.
At least with the Access database, you could have a few users adding and reading data at the same time without overwriting the whole file just for one change to a single field.
I realize that Microsoft is steering its developers to their mini desktop SQL server instead of Access but it just seems like a lot of overhead for the type of data being stored.
Today, all of the routines needed to read and write to an Access database is built into the existing DotNet Runtime. What drove me to this XML format is no longer a problem.
So, what do you think? Should we make the move back to the Access database to facilitate a better multi-user experience or stick with the XML?