Arise Software Ltd

Some facilities in GDMA/GDPro require a code, such as deleting transactions. Download this file for instructions to obtain the code.

Magic Code March2016.pdf (420.74 kb)

 

There is no fully automated way although we can assist with the process. The part we can automate is the exact name matching between Maori Land Online and GDPro/GDMA. We also automate any updates required as specified by the trustees. In a recent exercise, we completed a review of almost 240 owners and has taken over 5 hours. This does not include the review done by the trustees.

First we supply a spreadsheet:

In tab 1 (exact match)

This contains an exact name match between Maori Land Online and GDPro/GDMA. Share differences are highlighted. Trustees manually review and let us know, for each owner record in this tab, if we are to update GDMA shares to be the same as MLC shares.

In tab 2 (In MLC not GDPro)

This contains owners from Maori Land Online but not in GDMA.

Trustees manually review and let us know, for each owner record in this tab, if we to add the Maori Land Online record into GDPro/GDMA.

 In tab 3 (In GDPro not MLC)

This contains owners in GDPro/GDMA but not in Maori Land Online.

Trustees manually review and let us know, for each owner record in this tab, if we are to close the GDPro/GDMA owner record where there was not a match. Usually due to a succession. However, we then suppy a list of these closed records as these may contain outstanding money.

Name updates

Trustees may inform us of GDMA owner record name updates.

Updated List

We then resupply and updated owner list and shares to trustees to review. This process continues until the trustees are satisfied with the list.

Name matching

We have tried near name matching but found the results inadequate due to aliases, different spellings, different surname due to marriage, owners in trusts etc.

Here is the manual for doing successions

GDMA Successions Manual March 2016.pdf (1.54 mb)

http://arisesoftware.co.nz/Demos/Successions/Successions.html

SuccLetter.rpx (8.00 kb) (this allows for customisation of the succession letter)

 

Automatic installation (for existing installations)

• Simply restart GDMA and it should ask if you would like to update your version – click Yes. You can skip the rest of these instructions if it worked, otherwise try the manual installation below.

 Manual installation (for existing installations)

• Simply install using the install link provided in the email, in Internet Explorer (does not require administrative privileges)

• If can log into the application(s), please uninstall the prior version of the application via the control panel
  • Windows 7 uninstall instructions: https://www.google.co.nz/search?q=how+to+uninstall+an+application+using+windows+7
  • Windows 8 uninstall instructions: https://www.google.co.nz/search?q=how+to+uninstall+an+application+using+windows+8
  • Windows 10 uninstall instructions: https://www.google.co.nz/search?q=how+to+uninstall+an+application+using+windows+10

New installations

• Simply install using the install link provided in the email, in Internet Explorer (does not require administrative privileges)

• Please download the following – there is a file inside each of these that needs to be install (these will need admin privilege):
  • http://arisesoftware.co.nz/files/GDProReportingv2.zip
  • http://arisesoftware.co.nz/files/ActiveReportsSP4.zip

We create a GDMA application specifically for you. We need the following information to create the package:

• The “Computer Name” (https://www.google.co.nz/search?q=how+do+i+find+the+computer+name) of the server/computer/laptop that has MS SQL Server on it with the GDPro/GDMA database
• The SQL Server instance name (https://www.google.co.nz/search?q=how+do+i+find+the+sql+server+instance+name), typically SQLExpress.
• The Trust count
  • In GDPro or GDMA, go to administration, trusts, then count the number of trust records

We will then supply a link to download the GDMA application

• It uses the dsgdpro SQL Server login, that is the default login for GDPro and GDMA
• It is a click once application https://www.google.co.nz/search?q=what+is+click+once and does not install in your typical c:\programs files. What this means is each user profile that requires GDPro/GDMA needs to run the install.
• Click Once does not require admin privileges for installation

Considerations for ad-hoc reporting:

http://help.arisesoftware.co.nz/post/2015/08/28/gdpro-gdma-ad-hoc-reports-aren-t-working

Stuck with reporting?

There’s a report manual here that could help in your reporting enquiry: /post/2015/11/18/manuals

For more special one-off reports that you maybe able to do your self? /post/2015/11/26/gdpro-gdma-ad-hoc-reporting
And this will provide a great start to basic ad-hoc reporting: /post/2015/12/04/adhoc-reporting-of-shares

Ad-hoc reports not working in GDMA? Here’s something that will help /post/2015/08/28/gdpro-gdma-ad-hoc-reports-aren-t-working

If you need something more sophisticated, we can do a one-off report and add it to our development list here: http://arisesoftware.co.nz/News – no ETA at this stage.

To report on all shares for a block using the adhoc system, please watch this video

It then should look like this:

Click Preview in Grid once completed.

This report can be used to export addresses to MS Excel.

For all other reports that require each address line to be split.

First, the address needs to be in a single line. In this example, column D contains the address and column E has the formula that converts the multi line address to a single line =SUBSTITUTE(SUBSTITUTE(D2,CHAR(10),";"),CHAR(13),"")


The next step is to copy and paste column E to column F, as a value

The final step is to then use Excel to separate the individual address lines into their own columns.
https://support.office.com/en-us/article/Split-text-into-different-cells-30b14928-5550-41f5-97ca-7a3e9c363ed7

To get the full extent of reporting your information, using ad-hoc reporting will provide reporting and analysis solution to answer business questions "as the occasion requires" without having to request queries from IT or getting a report specifically developed.

http://www.logianalytics.com/resources/bi-encyclopedia/ad-hoc-reporting/

Here is a good start to understand the basic concept of doing database queries http://www.w3schools.com/sql/.
Doing similar one-to-one courses can cost hundreds, even thousands of dollars - so take this opportunity to do it at no cost.

We can make a day session for your area just for GDPro SQL. It will be a highly technical session specifically for GDPro database querying so it is important that the tutorials from http://www.w3schools.com/sql/ are mastered prior to the session.

The first half of the day will go over the GDPro database and the rest of the day doing examples provided by the group.

The following articles also need to be understood as GDPro/GDMA/Grants use Microsoft SQL Server relational database server technology:

• https://en.wikipedia.org/wiki/Database_server

• https://en.wikipedia.org/wiki/Relational_database

• https://en.wikipedia.org/wiki/Microsoft_SQL_Server

In the past, it was possible to put GDPro onto a laptop with the database in order to conduct an AGM at a location outside the organisation.

Support for GDPro on laptops

We no longer support GDPro out on laptops using a GDPro/GDMA database outside of the organisation, but we do GDMA. The reason is GDPro is becoming cumbersome to deploy due to the MS Access requirement and the changes Microsoft have made. GDMA installation is far less complicated and does not need special "rights" to have it installed.

For licensing reasons, GDPro/GDMA networked connectivity between machines that is outside the core office system is also not supported.

GDMA AGM Facility

GDMA has an AGM facility and there is a manual via the Help button (at the top) in GDMA.

We are also plan to create a package (free to licensed GDPro/GDMA organisations) that allows AGM functionality without the need of the GDPro/GDMA database. It is designed to:

• extract trust information (name, shid, address, shares) to a file,

• import the file to the AGM package on a laptop,

• record attendance on the laptop at the AGM,

• once the AGM is complete, extract the attendance information to a file

• import the attendance information from the file, back into GDPro/GDMA at the office

SQL Server version on the laptop

SQL Server on the laptop needs to be the same version as the main SQL Server used for GDPro/GDMA at the office. Otherwise it may not be possible to restore the database from the laptop back to the office.

SQL Server Database

1. Install SQL Server Management Studio to the Laptop
2. Backup the database from the live server
3. Restore the backup to the Laptop's SQL Server
4. Add the SQL Server login

Laptop GDMA application

We will create a GDMA application specifically for the laptop. We need to be provided the “Computer Name” (https://www.google.co.nz/search?q=how+do+i+find+the+computer+name) of the laptop and the SQL Server instance name (https://www.google.co.nz/search?q=how+do+i+find+the+sql+server+instance+name), typically SQLExpress.

Can we have an "Open" GDMA for our laptops?

We have to supply individual GDMA’s to be custom made for each individual database – otherwise, this allows an open door to other people using our package without giving us appropriate acknowledgement (aka fees) of the amount of time and effort that has gone into the development of the package.

GDPro is "Open"?

It may be open for GDPro, but that is so very much dated and it’s platform unsupported by Microsoft, we no longer support GDPro onto laptops. Hence, why we have put a lot of development into GDMA, to future proof the system.

Therefore, please let us know how many blocks are in the database and we’ll build a GDMA just for your specific laptop within 48 business hours.