Multiple Entries under same ID in ACCESS (1 Viewer)

[hrdpgajjar]

Hi all,
I have a Courier Register table which has following columns

1. Inward ID
2. Inward Date
2.Applications
3.Other Documents

Every day I received multiple applications (i.e. 10 per day) and 5 other documents for a one Inward ID. Inward ID must be only one for a day as we are mentioning the same ID in all documents for easy tracking.

Also I've to enter all this data under a single form only. How Can i do it?

How can i design the tables Can I manage all these under one table or I've to make multiple tables (child tables)

help me on this..

 

[arnelgp]

see this sample db I made for you.

 

[hrdpgajjar]

see this sample db I made for you.

Sir,
Thanks for prompt Reply and making a DB for me.

But my application & Other docs must be a separate tables, because application table must has columns like name of sender, date received, place of sender & farmer name...


same columns required in other docs table too..

I've already made separate tables but i am confused how to enter multiple applications under a same inward ID ?

main prob. is that I have to assign a unique number or inward number for all entries like in application table, in other docs table


I've also attached the excel sheet in which we maintain inward/outward.
Kindly suggest how can i convert it to Access



Help appreciated


Thanks

 

[arnelgp]

first unmerged all cells.
then identify the meanings of each column.
you have to apply normalization and
break each columns into separate tables.

you do the first.

 

[The_Doc_Man]

See my reply to your other post on the subject of locking autonumbers for a day.

You seriously need to read up on normalization because you are trying to use Access as a spreadsheet in a way that will prevent you from using it efficiently or effectively.

If you search this forum for "normalization" that would give you some good articles. If you search the general web, look for "database normalization" because there are at least five other topics that use the word "normalization" that have nothing to do with databases.