A
AD108
Forgive the double posting, but I think the first group I posted this in was
too obscure, with only few postings a day.
Hello,
I am just learning to develop apps with Access. I have a bit of experience
developing Excel apps, using VBA.
I need to design a Produce purchasing and distribution application. It will
need to handle incoming and outgoing product, invoice tracking, pricing,
etc.
I'm sure there's a million ways to do it, but my main question at this point
is how to set up the app to handle incoming orders, and retain those orders
until they are filled. My initial thought is to set up a table called
tblOpenOrders, that would relate to the Location, Incoming Orders and Item
Tables. I was going to make its primary key the Item Number field, from the
Item Table.
I was thinking to make an Open Order field in tblOpenOrders. The value
would increase with any incoming order recieved, and decrease with any order
filled, using some type of code or calculated field. Does this sound like a
good approach?
Thanks
Ariel
too obscure, with only few postings a day.
Hello,
I am just learning to develop apps with Access. I have a bit of experience
developing Excel apps, using VBA.
I need to design a Produce purchasing and distribution application. It will
need to handle incoming and outgoing product, invoice tracking, pricing,
etc.
I'm sure there's a million ways to do it, but my main question at this point
is how to set up the app to handle incoming orders, and retain those orders
until they are filled. My initial thought is to set up a table called
tblOpenOrders, that would relate to the Location, Incoming Orders and Item
Tables. I was going to make its primary key the Item Number field, from the
Item Table.
I was thinking to make an Open Order field in tblOpenOrders. The value
would increase with any incoming order recieved, and decrease with any order
filled, using some type of code or calculated field. Does this sound like a
good approach?
Thanks
Ariel