Installing Software

[pabloh007]

I know that a lot of the issues with installing software on the MLS lds computers has to do with conflicts with licensing etc.. If I create the software would I be able to install on the mls ward pc? I just got my calling was ward clerk and see my ward has a lot of manual work being done and saved in binders. I think it would be perfect for us to input this on a db and do away with the paper copies. I pretty much know a little about C# and SQlite and that is the route i'm thinking of going.

[aebrown]

I know that a lot of the issues with installing software on the MLS lds computers has to do with conflicts with licensing etc.. If I create the software would I be able to install on the mls ward pc? I just got my calling was ward clerk and see my ward has a lot of manual work being done and saved in binders. I think it would be perfect for us to input this on a db and do away with the paper copies. I pretty much know a little about C# and SQlite and that is the route i'm thinking of going.

It can certainly be helpful to install additional software on a ward administrative computer, created by you or by someone else. But you should exercise caution, too. Some things to be aware of are:

• The Stake Technology Specialist should be made aware of and approve any software installed.
• Software you develop yourself should have no licensing issues, but make sure that you carefully follow the licensing for any third-party libraries (compiled into your application, or runtime) or other dependent software (such as a DBMS).
• Any software that deals with confidential information should be properly secured -- it is not sufficient to depend on the physical access and system password for the administrative computer (note that MLS has passwords, too). Also make sure that confidential information is not uploaded to any public servers, even if it is encrypted.
• Think carefully about what how your application fits in with how you interact with the bishopric, other clerks, and other ward members who would use the application. Are you simplifying their lives, or requiring them to learn yet another application?
• Consider the impact on the ward after you are released. Will ward administrative processes have become dependent on the application? Will your successor be able to maintaintain it as changes need to be made to keep up with new versions of MLS or other policy changes that will certainly happen in the future?

[pabloh007]

Thanks that is very helpful upon designing the application, I usually use C# Express edition for user interface and Sqlite for the backend database.

[scott0912-p40]

I just got called into the Bishopric and see a lot of the same stuff that you are talking about. I am planning on writing a program that will automatically print off an sacrament agenda and keep track of who has talked/prayed to make life a little easier for the clerks. I am a C# developer so I might be able to help you. I am planning on importing the names/auxiliaries/callings into my data store. Then when I am typing the agenda up it will automatically fill names and callings (for releases and sustaining). Maybe we can share some ideas and come up with a better system.