CPC Program Database - Hingham
Municipality Information
Hingham
CPA Program Details
04-28-2001
1.5%
Low income, first $100,000 - residential
CPA Elections History
 
Election Purpose
Path to Ballot
Surcharge
%
Exemptions
Election Date
Status
% Yes
% No
Current
Status
 
  Revocation Ballot Question Petition 0%   11-07-2006 Fail 28% 72%  
  Initial Adoption Ballot Question Petition 1.5% Low income, first $100,000 - residential 04-28-2001 Pass 59% 41% Yes
CPA Revenue History
 
Fiscal
Year
Local
Surcharge
Total Trust
Fund
Distribution
Percentage
Total Revenue (Local
Surcharge +
Distribution)
 
  2002 $430,979     $430,979
  2003 $443,740 $430,979 100% $874,719
  2004 $483,468 $443,740 100% $927,208
  2005 $530,396 $483,468 100% $1,013,864
  2006 $592,087 $530,396 100% $1,122,483
  2007 $633,009 $592,087 100% $1,225,096
  2008 $663,816 $633,009 100% $1,296,825
  2009 $685,969 $448,874 67.62% $1,134,843
  2010 $758,955 $238,819 34.81% $997,774
  2011 $778,838 $206,450 27.2% $985,288
  2012 $789,854 $207,475 26.64% $997,329
  2013 $832,924 $211,950 26.83% $1,044,874
  2014 $868,237 $434,996 52.23% $1,303,233
  2015 $935,678 $273,191 31.5% $1,208,869
  2016 $978,723 $277,441 29.7% $1,256,164
  2017 $1,011,594 $201,390 20.58% $1,212,984
  2018 $1,046,814 $174,017 17.2% $1,220,831
  2019 $1,085,311 $199,050 19.01% $1,284,361
  2020 $1,122,659 $259,590 23.92% $1,382,249
  2021 $1,178,208 $321,379 28.63% $1,499,587
  2022 $1,221,650 $516,522 43.84% $1,738,172
  2023 $1,275,520 $470,474 38.51% $1,745,994
  2024 $1,463,718 $268,169 21.02% $1,731,887
  2025 $0 $264,363 18.06% $264,363
TOT   $19,812,148 $8,087,829   $27,899,977
Show fields from Show fields from Show fields from a related table
Report Name *
Description
Reports and Charts Panel
Each table has a panel listing its reports and charts, organized in groups.
Please wait while your new report is saved...
Field label
Column heading override
Justification
What does auto mean?
Fields in:

Fields to Extract:

Name for the new table:
Items in the new table are called:

When you bring additional fields into a conversion, Quickbase often finds inconsistencies. For example, say you're converting your Companies column into its own table. One company, Acme Corporation, has offices in New York, Dallas and Portland. So, when you add the City column to the conversion, Quickbase finds three different locations for Acme. A single value in the column you're converting can only match one value in any additional field. Quickbase needs you to clean up the extra cities before it can create your new table. To do so, you have one of two choices:

  • If you want to create three separate Acme records (Acme-New York, Acme-Dallas and Acme-Portland) click the Conform link at the top of the column.
  • If the dissimilar entries are mistakes (say Acme only has one office in New York and the other locations are data-entry errors) go back into your table and correct the inconsistencies—in this case, changing all locations to New York. Then try the conversion again.

Read more about converting a column into a table.

We're glad you're interested in doing more with Quickbase!

Now we need to make you official before you share apps or manage your account.

Verifying your email lets you share Quickbase with others in your company.

Your work email
Your company