What I’m trying to do:
I am trying to understand/learn [workflow, design ideas, coding]
How to go about building Stock/Invoice app?
These are questions coming to my mind since I started reading forum.
Link table or Simple Object?
I come from background where primary key and foreign key was a thing.
Bulk of data manipulation server side or client side?
Now lets actually think about app
I run small computer/gaming shop first thing I deal everyday bases is accounting. Thus Stock/Invoice App.
Process [my thought] - During filter process I can easily drill down so linked table.
Client give rolls of sticker → One bill came in - > record client details, bill no and items inside that bill.
Database Design [client table] → relation [one to many] to bill [gpbillno] here I used linked table to single row->[gpbillno] store bill no and link to client name. →
[gpbillno] is linked to [items] one to many using linked tale to single row.
now keeping records 3 rolls came in for printing, size in meters[3, 2, 4] total 9
after printing 1 roll sent back to client new hsn number is given to items and invoice is printed. In hand Stock 2 rolls are left.
Database Design: - Using this table stock in and out will be tracked
[transactions] table keeps record of date and time, rolls quantity and meters are tracked as in and out here and this table is linked to client, items, gpbillno.
Give me ideas for better database design or how to simplify my app.
Any ideas and improvements will be welcomed. If I am making app complicated let me know that too.
So far what I have done is used CRUD Example and created data grid 4 times around table to repeat myself [Anki - idea time and space repetitions]
Clone link: