The Church of Jesus Christ of Latter-day Saints

I have a couple more questions about your ward map program. It has really helped. Today I completed entering Stake geocodes for the entire Stake. Ward maps was very helpful in mapping and assigning those geocodes. I just now have some cleanup to do and getting the Wards to find missing addresses. Re...

Thanks for the info. I think I am stressing your Ward Map tool using it for the whole Stake but it is hanging in there. It works really good to have a seperate file for the region definitions. I do have a couple more questions. 1- I am having problems with addresses that contain an apartment number....

hpaulsen I downloaded your ward map tool. So far it looks like it will work for us since maps under LDS.org tools are having problems. I do have a couple of questions. 1- I assume the data loaded stays on our computer and is not put out is cyberspace, correct? 2- In the lower right hand corner there...

We are starting a Stake geocoding task. Our decision has been to enter a Stake geocode for each household in order to use the boundary realignment tools within MLS when it comes time to examine boundaries. At first glance, I was excited to see the "maps" selection on LDS.org. It seemed like a great ...

How did you export this information. I don't see anyway to export the geocode report in boundary realignment. I looked at customer reports but got an entry for every member instead of just households. Any help would be appreciated. Thanks

Sometimes when accessing the calendars setting page I get a distorted view. Sometimes it comes up fine. I am using Google Chrome. See attachment for a screen shot.

We have taken a rather simplistic approach to webcasting. We just finished our 5th webcast. We have tweaked our configuration a little over time and it is working well for us. Here is our configuration. 1- Computer - HP G42 laptop running Windows 7. At medium resolution the CPU is at 50%. I have set...

Thanks for the reply. I discovered this same work around. I hope the developers can fix this problem so we don't have to have a work around.

We are starting our scheduling for 2013. The thought was that we would edit the recurring events and extend the end date to 31 Dec 2013. For 2012, the end date had been set to 31 Dec 2012. This action places the recurring events on the 2013 calendar however all location information is lost. We tried...

In our Stake we gave every unit access to schedule at every building. Our approach was to make it as wide open as possible and then monitor for problems. So far, it has worked really well with no noted problems.