Municipality Information
Ashland
CPA Program Details
05-07-2002
3%
Low income, first $100,000 - residential
CPA Elections History
 
Election Purpose
Path to Ballot
Surcharge
%
Exemptions
Election Date
Status
% Yes
% No
Current
Status
 
  Modify Exemptions Legislative Body Vote 3% Low income, first $100,000 - residential 05-02-2006 Pass 64% 36% Yes
  Initial Adoption Legislative Body Vote 3% First $100,000 - residential 05-07-2002 Pass 51% 49%  
  Initial Adoption Ballot Question Petition 3% First $100,000 - residential 05-01-2001 Fail 33% 67%  
CPA Revenue History
 
Fiscal
Year
Local
Surcharge
Total Trust
Fund
Distribution
Percentage
Total Revenue (Local
Surcharge +
Distribution)
 
  2002       $0
  2003 $452,091     $452,091
  2004 $499,082 $452,091 100% $951,173
  2005 $568,794 $499,082 100% $1,067,876
  2006 $644,325 $568,794 100% $1,213,119
  2007 $668,383 $644,325 100% $1,312,708
  2008 $672,641 $668,383 100% $1,341,024
  2009 $685,288 $523,858 77.88% $1,209,146
  2010 $689,903 $294,205 42.93% $984,108
  2011 $709,125 $231,189 33.51% $940,314
  2012 $723,403 $239,117 33.72% $962,520
  2013 $733,816 $245,452 33.91% $979,268
  2014 $765,979 $489,834 66.75% $1,255,813
  2015 $804,072 $307,361 40.1% $1,111,433
  2016 $855,303 $302,282 37.7% $1,157,585
  2017 $903,214 $223,121 26.09% $1,126,335
  2018 $975,640 $196,379 21.77% $1,172,019
  2019 $1,019,346 $236,204 24.21% $1,255,550
  2020 $1,100,959 $307,172 30.13% $1,408,131
  2021 $1,151,483 $395,255 35.9% $1,546,738
  2022 $1,228,844 $634,114 55.07% $1,862,958
  2023 $1,243,243 $591,508 48.14% $1,834,751
  2024 $0 $328,647 26.43% $328,647
TOT   $17,094,935 $8,378,373   $25,473,308
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