Design a DB to Track Import Permit Goods (Shipping Items from different countries) (1 Viewer)

ashraful

New member
Local time
Tomorrow, 06:11
Joined
Dec 6, 2017
Messages
9
Dear all,

I need to design a Database for the Import Permit Goods that is shipped in our Project from different countries. Number of items are huge; more than 500K items will be shipped in the project. These items needs to be in a database so that each item can be tracked in future.

I have attached an Excel file.

There are 30 fields that needs to be filled. Among these 30 fields, 9 fields are related to Goods that will be imported in the Project.

Please, help me design a form.

Thanks
 

Attachments

  • Tracking Register for Imported Goods.xlsx
    29.7 KB · Views: 77

jdraw

Super Moderator
Staff member
Local time
Today, 19:11
Joined
Jan 23, 2006
Messages
15,364
Here is info on Database Planning and Design.
it is very important to get your tables and relationships set up to match your business rules. I recommend you create a data model (pencil and paper), use some sample data and test scenarios to adjust/validate your model --then build the physical database.

You haven't said but do you:
-have multiple points of entry of goods into your project (multi user/multi location)
-have a complete list of items to be tracked
-sample reports for tracking info output including level of detail/summary/grouping
-understand business rules
-have experience with Normalization.

Good luck with your project.
 

ashraful

New member
Local time
Tomorrow, 06:11
Joined
Dec 6, 2017
Messages
9
- single user database
- we are preparing a complete list of items
- at present, we are not planning on output.

Data Entry part is the biggest challenge now. That’s why looking for a Form Design at first.
Please, advise.
 

jdraw

Super Moderator
Staff member
Local time
Today, 19:11
Joined
Jan 23, 2006
Messages
15,364
You are being short-sighted, but I do understand priorities.
What info do you need to track? What groupings etc?
Can you get the data you need from the table(s) you have designed?

Read up on Normalization.
Build a model and test it, before building the physical database.

You can continue with your current mechanism for data capture, and
get your tables designed, then your data input form.

Test at every step. It is more difficult to adjust/redesign a physical database than a data model on paper. It's analogous to a blueprint for a house. Change a line on the paper, or move a physical wall?????????????
 

Users who are viewing this thread

Top Bottom