I am working with a business and they are going to want me to write them a purchase order program within Access 2010. Can anyone point me in the direction where I can start teaching myself how to do this. I am not a pro at Access by any means but I can do alot of stuff within the program. Any help would be appreciated.
Purchase Order Program
- Thread starter Toledo123
- Start date
boblarson
Smeghead
- Local time
- Yesterday, 19:19
- Joined
- Jan 12, 2001
- Messages
- 32,059
First off, you can look here for a potential data model to use or modify for your use:
http://www.databaseanswers.org/data_models/purchase_orders/index.htm
http://www.databaseanswers.org/data_models/purchase_orders/index.htm
Boblarson's response is very detailed. That website outlines many important aspects such as what is the main thing you are looking to track.
Think about what you want to track: Vendors, Customers, Purchase Orders, Purchase Order Details, Employees, Products, Etc.
Research, brainstorm, write it down, and develop your tables.
There are also a ton of examples on this site. Plus check out these youtube videos, they helped me with alot with the basics.
Boblarson also helped along the way with my projects, as well as everyone else that contributes to this wonderful site!
Think about what you want to track: Vendors, Customers, Purchase Orders, Purchase Order Details, Employees, Products, Etc.
Research, brainstorm, write it down, and develop your tables.
There are also a ton of examples on this site. Plus check out these youtube videos, they helped me with alot with the basics.
Boblarson also helped along the way with my projects, as well as everyone else that contributes to this wonderful site!
AC5FF
Registered User.
- Local time
- Yesterday, 21:19
- Joined
- Apr 6, 2004
- Messages
- 552
Toledo
I've got a customized PO database I use here at work.
I could look into stripping data from it and passing it along, but not sure how much that would help. It's tied into other DBs (like Inventory and Production) and without those DBs as well - at least for me - using a stripped down version has always been tough.
A agree with steve though; research and brainstorm everything you want to track. It will help in the long run. I inherited the DBs when I got hired, but I find I constantly have to modify them because this or that was not though of and implemented from day one....
I've got a customized PO database I use here at work.
I could look into stripping data from it and passing it along, but not sure how much that would help. It's tied into other DBs (like Inventory and Production) and without those DBs as well - at least for me - using a stripped down version has always been tough.
A agree with steve though; research and brainstorm everything you want to track. It will help in the long run. I inherited the DBs when I got hired, but I find I constantly have to modify them because this or that was not though of and implemented from day one....
