dearsir,
i really understood how nz() function and what the null values can be
in detail i would like to have your kind advise for the data base im
creating .
im creating an data base with 16 tables what makes me worried is .
(1) all the tables data is necessery to get final report, but the user will
not enter
any data ina table where there is not necessery . like, in a dabase of an
social welfare organisation which have detailes of donations recevived and
its transaction like
table banktransaction and / or
table income tax paid and
table governament help received
but these tables i have to include in final statement query
but if the organisation not had any transaction / nor received any govt
help normally the user will not touch such forms and inturn it couses the
whole finalreport query to collape
You can use "Left Joins" in queries to display records from the "one" side
table even if there are no matching records in the "many" - select the join
line in the query design window and choose Option 2, "show all records in
<main table> and matching records in <child table>". Depending on how your
tables are structured, this can cause other errors; it is the right technique,
but it must be done correctly.
One concern: There is a strong temptation to look at the desired appearance of
the "final report" and let that drive your table design. This is generally
going to give you a set of *very badly designed tables*. The layout of the
Report should come LAST, after the Tables are correctly normalized based on
the logical structure of the data in the tables. You very well may have done
so, I can't tell from this post... but it's a very common error starting out
with Access.
(2) and all my tables have no related fields to establish fine link of
relation ships
most PK fields are generated keys hence i created relationships in QBE
window
If your tables have no related fields to link, *you do not have a
database*!!!!! You have a bunch of unrelated stacks of data! If you are
dealing with an Organization with multiple Transactions, say, then you must -
no option! - include a link to the Organization in the Transactions table in
order for Access to know which organization originated these transactions.
(3) how to come out of such herdles
Design your tables and their relationships correctly, *first*, before starting
to even think about forms.
(4) it is necessery for me to give the previes year closing balence and the
present year opening balences and the present yesr closing balences
hence the date criteria as very essential for me to use in every table
query
That's not a question; that's a true statement. Yes, date criteria are
essential; each table which contains date-sensitive data should have a
required date field. Since I don't know your business model nor the contents
of your tables, nor even what date problems you're having, I can't be more
specific than that.
kindly advise to over come such probloms
thanking you sir,
This is asking a LOT: starting with the basic fundamental table design. I
would really suggest that you try to find a local expert for hire to help you
set this up.
For some tutorials and introduction to relational theory, if you haven't
already done so consider looking at some of the links in:
Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html
The Access Web resources page:
http://www.mvps.org/access/resources/index.html
A free tutorial written by Crystal (MS Access MVP):
http://allenbrowne.com/casu-22.html
MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials
John W. Vinson [MVP]