By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,491 Members | 879 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,491 IT Pros & Developers. It's quick & easy.

Bring data from a form to another form when an event is trigger

P: 4
Hi,

I currently working on a simple Inventory Tracking System. I have 12 form to input and calculate balance for 12 different material. I have a form act as a main menu to go to this 12 form. The input from the form is store in 12 respective table . In each of the 12 form I have include a trigger whereby when the event of inventory reach it lowest balance/limit (i set it as 100) a message box would prompt out telling user to order more inventory.

My Supervisor wanted a new request is when the event happen (the msg box prompt out) in the meantime the item name, date and the balance to be send to the main menu form. So whenever user open main menu form they know which inventory in need of re-ordering. Could this be done...??

I have attach my database hoping someone can guide me to finish this request. I reli need help on solving this problem. Been stuck for a long time.Thank You.
Attached Files
File Type: zip Tracking System (All)_Backup.zip (491.5 KB, 47 views)
Mar 12 '10 #1
Share this Question
Share on Google+
3 Replies


mshmyob
Expert 100+
P: 903
Oh my..... I would suggest you read up on normalization.

cheers,
Mar 12 '10 #2

P: 4
Erm... by normalization do u mean i should store my data into 1 table... If can i wish u could explain more to me about wat should i do to make database more efficient.... Thank...
Mar 12 '10 #3

mshmyob
Expert 100+
P: 903
No.

First write down what you want this database to do. Then each entity (subject - each set of related data) of your database needs a table with a primary key.

For instance not knowing exactly what your database is for or what you are trying to accomplish I can see you need a table for :

Operator
M/C
Shift
Component (I don't know what Capillary, Lead Frame, etc. is so I will just say they are components)

and more tables for to tracking inventory and the time etc.

But you need a good explanation of database before coming up with a final design.

You do not create a form for every component you have and hard code combo boxes to pick operators, M/C, etc.

Again read the article on normalization.

cheers,
Mar 14 '10 #4

Post your reply

Sign in to post your reply or Sign up for a free account.