TaxableValue Not Displaying

[goslincm]

I have:

tbl_DistressFactors
pk = RecordID
fk = CLU_Code
fk = CTV_ID

tbl_TaxableValue
pk = CLU_Code
fk = CTV_ID

tbl_CTV_MUNFIN
pk = CTV_ID
fk = CLU_Code

This has both my CTV_ID and CLU_Code feeding into my DistressFactors table, but I cannot get my TaxableValue field from my taxablevalue table to feed into it.

What am I missing?

 

[ThomasLafferty]

I'm not following your syntax here:
by pk=RecordID do you mean that pk is the name of the field and its purpose is to serve as the ID?

If so, it looks like you have repeated field names. Probably the next place to look (assuming I misunderstood your names) is at the relationships window.

Make sure there is a relationship between CTV_ID in both tables.

If there isn't one, create it by dragging CTV_ID from tbl_TaxableValue to CTV_ID in tbl_DistressFactors. Enforce the referential integrity and check cascade update and cascade delete.

Are you getting an error msg? Inputting data and nothing is happening? What is the issue?

Tom

Live once die twice; live twice die once.

 

[goslincm]

RecordID was the name of the field and its purpose was to serve as the ID. I thought I needed that in the DistresFactors table.

In my relationship window I had already established a relationship between tbl_TaxableValue and tbl_DistressFactors via the CLU_ID. Are you saying I should delete that and instead have CTV_ID only?

I do not get an error message but rather nothing displays in my control for taxable value, its just empty.

 

[lespaul]

your table structure doesn't make any sense!!

tbl_DistressFactors
pk = RecordID
fk = CLU_Code
fk = CTV_ID

tbl_TaxableValue
pk = CLU_Code
fk = CTV_ID

tbl_CTV_MUNFIN
pk = CTV_ID
fk = CLU_Code

other than the fact that the PK and FK are reversed, what's the difference between tbl_TaxableValue and tbl_CTV_MUNFIN?

Is the CLU_Code FK in the first table reference the CLU_Code in the tax table or the MUNFIN table?

Have you read the fundamentals document linked below? One of the main purposes of a database is to store information in a single place. You appear to have the same information in multiple places.


Leslie

Anything worth doing is a lot more difficult than it's worth - Unknown Induhvidual

Essential reading for anyone working with databases:
The Fundamentals of Relational Database Design
Understanding SQL Joi

 

[goslincm]

I need to find a way to relate tbl_distressfactors to each of the other two tables.

tbl_distress factors will consist of:

GenFundRev
GenFundExp
OperatingDeficit
CapitalFund
SpecialFund

The table will have the information entered daily based on monthly audits and will consist of information coming from villages, townships, cities and counties.

Tbl_taxablevalue

year1 real taxable value

information will come once a year, from cities and townships and be entered here

Currently the munfin table has codes for villages, its primary code is CLU_Code

Another tbl_CTV has the codes for cities and townships, its primary key is CTV_ID

At the end of the fiscal year, all units of government have to have comparisons computed using the taxable value from say 2003 compared to 2005 (gain or loss) against general fund growth or loss.

 

[goslincm]

I am new and inexperienced at this but I'm not giving up. I'll try a new route perhaps and with your feedback I'll get it.

What about instead of all the above tables, I merely have 1 with the following fields:

tbl_Main:
unitname-primary key
year-primary key
population
taxablevalue
generalfundrev
generalfundexp
capitalfundbal
specialfundbal

Given that I already have a table with the unit names and another table with the taxable values, can I create those two fields as look up fields pointing to those tables?

My other question would be can I upon looking up a particular unit name and/or tax value, can I have those values feed into the above table?

Not giving up

 

[lespaul]

Have you read the fundamentals document linked below? It really helps explain how to normalize your table structure.

First you have to identify your entities, it appears that you have municipalities, Funds, TaxableValues. Then you have to identify the attributes, what entity does each piece of data belong too. Municipalities have a population - so that's the table that piece of data goes into. TaxableValue - is that the average taxable value for property in the municipality? Then that data also goes into the municipality table....it could be that you are getting a record for each piece of property the municipality and this is the taxable value for the property. In that case you would need another table (entity) Property and the value of TaxableValue would belong to that table.

So, it is really impossible for us to really help you design your tables without knowing exactly what you are trying to do. So read the document below and post back after you have constructed your tables with all your table and field names and ask for assistance with the fine tuning.

Leslie

Anything worth doing is a lot more difficult than it's worth - Unknown Induhvidual

Essential reading for anyone working with databases:
The Fundamentals of Relational Database Design
Understanding SQL Joi