|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
July 27th, 2007, 07:02 PM
posted to microsoft.public.access.queries
|
|||
|
|||
Please suggest relationships model
What I need to do:
I have some rather expensive inventory items that I need to keep track of. These are to be used in several projects (jobs). I'm trying to design a simple database to help me keep track of where everything goes, so I can bill the right job for the right products. More Details: Inventory items have an ID, and description. I need to know how many of each item I still have remaining. Jobs have unique ID numbers (I dont want to use autonumber for this). I was thinking maybe I could design something that would sort of do transactions. Assign a transaction ID (Autonumber is ok), A date, a project # (job#) and how many of each of the inventory items were transfered on that date, or transaction. I did a little designing, and came up with three tables. Inventory |_ ID |_ Description |_ Quatntity on hand (??) Jobs |_ ID |_ Address Transactions |_ ID (autonumber ok) |_ Date |_ Quantity |_ Description Can someone suggest an efficient relationships model to make this work? Thanks in advance -- Moe 
|
|
#3
July 27th, 2007, 09:37 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Please suggest relationships model
Moe,
Below is a few links to help you get started... Please note, this FREE newsgroup provided by Microsoft would NEVER dream of charging you. Everyone (well almost everyone) VOLUNTEERS their time to provide FREE support and assistance. Ms Access Fundamentals: http://www.functionx.com/access/ Samples downloads: http://www.rogersaccesslibrary.com/TableOfContents3.asp Code, sample downloads, sample coding (I love this site): http://www.mvps.org/access/ Data model samples: http://www.databasedev.co.uk/data_models.html -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II "Moe" wrote in message ... What I need to do: I have some rather expensive inventory items that I need to keep track of. These are to be used in several projects (jobs). I'm trying to design a simple database to help me keep track of where everything goes, so I can bill the right job for the right products. More Details: Inventory items have an ID, and description. I need to know how many of each item I still have remaining. Jobs have unique ID numbers (I dont want to use autonumber for this). I was thinking maybe I could design something that would sort of do transactions. Assign a transaction ID (Autonumber is ok), A date, a project # (job#) and how many of each of the inventory items were transfered on that date, or transaction. I did a little designing, and came up with three tables. Inventory |_ ID |_ Description |_ Quatntity on hand (??) Jobs |_ ID |_ Address Transactions |_ ID (autonumber ok) |_ Date |_ Quantity |_ Description Can someone suggest an efficient relationships model to make this work? Thanks in advance -- Moe
|
|
#4
July 27th, 2007, 09:38 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Please suggest relationships model
I was kind of hoping not to have to purchase any software for this...
Excel could do the job, but an access database would be so much better organized. -- Moe "Steve" wrote: I have assumed that your inventory items are consumable and periodically you purchase items to replenish your inventory. TblJob JobID JobNumber JobDescription Job Address fields TblItem ItemID ItemDesc QuantityOnHand TblItemToJob ItemToJobID JobID ItemToJobDate TblJobItem JobItemID ItemToJobID ItemID Quantity JobItemAssignedCost TblItemVendor ItemVendorID VendorName Vendor contact fields TblVendorItem VendorItemID ItemVendorID ItemID ItemCost TblItemPurchase ItemPurchaseID ItemVendorID PurchaseDate PurchaseOrderNumber TblItemPurchaseDetail ItemPurchaseDetailID ItemPurchaseID ItemID Quantity UnitCost If you need help, I can help you for a very reasonable fee. Contact me at my email address below. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Moe" wrote in message ... What I need to do: I have some rather expensive inventory items that I need to keep track of. These are to be used in several projects (jobs). I'm trying to design a simple database to help me keep track of where everything goes, so I can bill the right job for the right products. More Details: Inventory items have an ID, and description. I need to know how many of each item I still have remaining. Jobs have unique ID numbers (I dont want to use autonumber for this). I was thinking maybe I could design something that would sort of do transactions. Assign a transaction ID (Autonumber is ok), A date, a project # (job#) and how many of each of the inventory items were transfered on that date, or transaction. I did a little designing, and came up with three tables. Inventory |_ ID |_ Description |_ Quatntity on hand (??) Jobs |_ ID |_ Address Transactions |_ ID (autonumber ok) |_ Date |_ Quantity |_ Description Can someone suggest an efficient relationships model to make this work? Thanks in advance -- Moe
|
|
#5
July 27th, 2007, 09:47 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Please suggest relationships model
Yes, Access is the preferred choice! You can start with the tables I
suggested, modify fields to suit and build from there. If you get stuck, you can post questions to the newsgroup. I offered my help if you wanted to get your database up and running as quick and painless as possible. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Moe" wrote in message ... I was kind of hoping not to have to purchase any software for this... Excel could do the job, but an access database would be so much better organized. -- Moe "Steve" wrote: I have assumed that your inventory items are consumable and periodically you purchase items to replenish your inventory. TblJob JobID JobNumber JobDescription Job Address fields TblItem ItemID ItemDesc QuantityOnHand TblItemToJob ItemToJobID JobID ItemToJobDate TblJobItem JobItemID ItemToJobID ItemID Quantity JobItemAssignedCost TblItemVendor ItemVendorID VendorName Vendor contact fields TblVendorItem VendorItemID ItemVendorID ItemID ItemCost TblItemPurchase ItemPurchaseID ItemVendorID PurchaseDate PurchaseOrderNumber TblItemPurchaseDetail ItemPurchaseDetailID ItemPurchaseID ItemID Quantity UnitCost If you need help, I can help you for a very reasonable fee. Contact me at my email address below. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Moe" wrote in message ... What I need to do: I have some rather expensive inventory items that I need to keep track of. These are to be used in several projects (jobs). I'm trying to design a simple database to help me keep track of where everything goes, so I can bill the right job for the right products. More Details: Inventory items have an ID, and description. I need to know how many of each item I still have remaining. Jobs have unique ID numbers (I dont want to use autonumber for this). I was thinking maybe I could design something that would sort of do transactions. Assign a transaction ID (Autonumber is ok), A date, a project # (job#) and how many of each of the inventory items were transfered on that date, or transaction. I did a little designing, and came up with three tables. Inventory |_ ID |_ Description |_ Quatntity on hand (??) Jobs |_ ID |_ Address Transactions |_ ID (autonumber ok) |_ Date |_ Quantity |_ Description Can someone suggest an efficient relationships model to make this work? Thanks in advance -- Moe
|
|
#6
July 27th, 2007, 10:05 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Please suggest relationships model
Do-it-yourself is not always the best decision. In fact, it can be a very
poor decision. Yes, from only the database point of view, if you create a database and it works for you, do it yourself is cheapest. From a business perspective, it can be much more expensive than hiring someone to build the database for you. The do-it-yourself route requires dedicated time and effort which means taking the time and effort away from something else. If you could have spent that time in a more profitable way such as increasing sales, the database cost you the value of the lost sales and that could easily be many times the fees you would have paid someone to create the database for you. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Gina Whipp" wrote in message ... Moe, Below is a few links to help you get started... Please note, this FREE newsgroup provided by Microsoft would NEVER dream of charging you. Everyone (well almost everyone) VOLUNTEERS their time to provide FREE support and assistance. Ms Access Fundamentals: http://www.functionx.com/access/ Samples downloads: http://www.rogersaccesslibrary.com/TableOfContents3.asp Code, sample downloads, sample coding (I love this site): http://www.mvps.org/access/ Data model samples: http://www.databasedev.co.uk/data_models.html -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II "Moe" wrote in message ... What I need to do: I have some rather expensive inventory items that I need to keep track of. These are to be used in several projects (jobs). I'm trying to design a simple database to help me keep track of where everything goes, so I can bill the right job for the right products. More Details: Inventory items have an ID, and description. I need to know how many of each item I still have remaining. Jobs have unique ID numbers (I dont want to use autonumber for this). I was thinking maybe I could design something that would sort of do transactions. Assign a transaction ID (Autonumber is ok), A date, a project # (job#) and how many of each of the inventory items were transfered on that date, or transaction. I did a little designing, and came up with three tables. Inventory |_ ID |_ Description |_ Quatntity on hand (??) Jobs |_ ID |_ Address Transactions |_ ID (autonumber ok) |_ Date |_ Quantity |_ Description Can someone suggest an efficient relationships model to make this work? Thanks in advance -- Moe
|
|
#7
July 27th, 2007, 10:23 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Please suggest relationships model
Steve,
If this is a reply to my eMail then please don't try to explain your soliciting to me. It is wrong in a FREE peer-to-peer newsgroup. I 'write' databases and have been doing so for 10 years. Right now, I am doing 6 contracts and am looking for help but it would never even occur to me to advertise for help here! And NEVER, let me me repeat that, NEVER have I ever tried to solicit work from this FREE newsgroup or any other FREE newsgroup unless they supply a section to do just that. I don't show my eMail address, no links to my site, NADA, NOTHING, ZILCH... well, you get the idea, because that is not why these groups are here! I will also note, that I get my work by word-of-mouth and have to provide my web page... AND even if I ran out of work tomorrow, I would NEVER solicit here! I come to here to get help and give help when I can. I come here to learn, share and sometimes get a good chuckle! I don't come here to post my resume or sell my services. So please, don't offer your lame reasoning for trying to drum up business. If contracting is not working for you get another job until something comes along. -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II "Steve" wrote in message ink.net... Do-it-yourself is not always the best decision. In fact, it can be a very poor decision. Yes, from only the database point of view, if you create a database and it works for you, do it yourself is cheapest. From a business perspective, it can be much more expensive than hiring someone to build the database for you. The do-it-yourself route requires dedicated time and effort which means taking the time and effort away from something else. If you could have spent that time in a more profitable way such as increasing sales, the database cost you the value of the lost sales and that could easily be many times the fees you would have paid someone to create the database for you. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Gina Whipp" wrote in message ... Moe, Below is a few links to help you get started... Please note, this FREE newsgroup provided by Microsoft would NEVER dream of charging you. Everyone (well almost everyone) VOLUNTEERS their time to provide FREE support and assistance. Ms Access Fundamentals: http://www.functionx.com/access/ Samples downloads: http://www.rogersaccesslibrary.com/TableOfContents3.asp Code, sample downloads, sample coding (I love this site): http://www.mvps.org/access/ Data model samples: http://www.databasedev.co.uk/data_models.html -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II "Moe" wrote in message ... What I need to do: I have some rather expensive inventory items that I need to keep track of. These are to be used in several projects (jobs). I'm trying to design a simple database to help me keep track of where everything goes, so I can bill the right job for the right products. More Details: Inventory items have an ID, and description. I need to know how many of each item I still have remaining. Jobs have unique ID numbers (I dont want to use autonumber for this). I was thinking maybe I could design something that would sort of do transactions. Assign a transaction ID (Autonumber is ok), A date, a project # (job#) and how many of each of the inventory items were transfered on that date, or transaction. I did a little designing, and came up with three tables. Inventory |_ ID |_ Description |_ Quatntity on hand (??) Jobs |_ ID |_ Address Transactions |_ ID (autonumber ok) |_ Date |_ Quantity |_ Description Can someone suggest an efficient relationships model to make this work? Thanks in advance -- Moe
|
|
#8
July 27th, 2007, 10:28 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Please suggest relationships model
Good advice, Steve.
May I add that the quality you get from a competent professional will be superior to what you can do your self. It is interesting how many people will try to write their own software. So why don't they do their own surgery? BTW, glad to see you out here playing by the rules and offering informed help to others. Keep up the good work.. -- Dave Hargis, Microsoft Access MVP "Steve" wrote: Do-it-yourself is not always the best decision. In fact, it can be a very poor decision. Yes, from only the database point of view, if you create a database and it works for you, do it yourself is cheapest. From a business perspective, it can be much more expensive than hiring someone to build the database for you. The do-it-yourself route requires dedicated time and effort which means taking the time and effort away from something else. If you could have spent that time in a more profitable way such as increasing sales, the database cost you the value of the lost sales and that could easily be many times the fees you would have paid someone to create the database for you. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Gina Whipp" wrote in message ... Moe, Below is a few links to help you get started... Please note, this FREE newsgroup provided by Microsoft would NEVER dream of charging you. Everyone (well almost everyone) VOLUNTEERS their time to provide FREE support and assistance. Ms Access Fundamentals: http://www.functionx.com/access/ Samples downloads: http://www.rogersaccesslibrary.com/TableOfContents3.asp Code, sample downloads, sample coding (I love this site): http://www.mvps.org/access/ Data model samples: http://www.databasedev.co.uk/data_models.html -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II "Moe" wrote in message ... What I need to do: I have some rather expensive inventory items that I need to keep track of. These are to be used in several projects (jobs). I'm trying to design a simple database to help me keep track of where everything goes, so I can bill the right job for the right products. More Details: Inventory items have an ID, and description. I need to know how many of each item I still have remaining. Jobs have unique ID numbers (I dont want to use autonumber for this). I was thinking maybe I could design something that would sort of do transactions. Assign a transaction ID (Autonumber is ok), A date, a project # (job#) and how many of each of the inventory items were transfered on that date, or transaction. I did a little designing, and came up with three tables. Inventory |_ ID |_ Description |_ Quatntity on hand (??) Jobs |_ ID |_ Address Transactions |_ ID (autonumber ok) |_ Date |_ Quantity |_ Description Can someone suggest an efficient relationships model to make this work? Thanks in advance -- Moe
|
|
#9
July 27th, 2007, 11:21 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Please suggest relationships model
Still thick as a brick.
These newgroups are for FREE peer to peer support. The only thing worse than an amatuer create his own database is to have the amatuer helped by steve at a "reasonable fee". This stuff is not rocket science and most reasonably intelligent people can create an adequate solution. John... Visio MVP "Steve" wrote in message ink.net... Yes, Access is the preferred choice! You can start with the tables I suggested, modify fields to suit and build from there. If you get stuck, you can post questions to the newsgroup. I offered my help if you wanted to get your database up and running as quick and painless as possible. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Moe" wrote in message ... I was kind of hoping not to have to purchase any software for this... Excel could do the job, but an access database would be so much better organized. -- Moe "Steve" wrote: I have assumed that your inventory items are consumable and periodically you purchase items to replenish your inventory. TblJob JobID JobNumber JobDescription Job Address fields TblItem ItemID ItemDesc QuantityOnHand TblItemToJob ItemToJobID JobID ItemToJobDate TblJobItem JobItemID ItemToJobID ItemID Quantity JobItemAssignedCost TblItemVendor ItemVendorID VendorName Vendor contact fields TblVendorItem VendorItemID ItemVendorID ItemID ItemCost TblItemPurchase ItemPurchaseID ItemVendorID PurchaseDate PurchaseOrderNumber TblItemPurchaseDetail ItemPurchaseDetailID ItemPurchaseID ItemID Quantity UnitCost If you need help, I can help you for a very reasonable fee. Contact me at my email address below. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Moe" wrote in message ... What I need to do: I have some rather expensive inventory items that I need to keep track of. These are to be used in several projects (jobs). I'm trying to design a simple database to help me keep track of where everything goes, so I can bill the right job for the right products. More Details: Inventory items have an ID, and description. I need to know how many of each item I still have remaining. Jobs have unique ID numbers (I dont want to use autonumber for this). I was thinking maybe I could design something that would sort of do transactions. Assign a transaction ID (Autonumber is ok), A date, a project # (job#) and how many of each of the inventory items were transfered on that date, or transaction. I did a little designing, and came up with three tables. Inventory |_ ID |_ Description |_ Quatntity on hand (??) Jobs |_ ID |_ Address Transactions |_ ID (autonumber ok) |_ Date |_ Quantity |_ Description Can someone suggest an efficient relationships model to make this work? Thanks in advance -- Moe
|
|
#10
July 27th, 2007, 11:30 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Please suggest relationships model
cheeezzzze!
Right after I compliment him on his good behavior over the last couple of weeks. I guess some people just never learn. -- Dave Hargis, Microsoft Access MVP "John Marshall, MVP" wrote: Still thick as a brick. These newgroups are for FREE peer to peer support. The only thing worse than an amatuer create his own database is to have the amatuer helped by steve at a "reasonable fee". This stuff is not rocket science and most reasonably intelligent people can create an adequate solution. John... Visio MVP "Steve" wrote in message ink.net... Yes, Access is the preferred choice! You can start with the tables I suggested, modify fields to suit and build from there. If you get stuck, you can post questions to the newsgroup. I offered my help if you wanted to get your database up and running as quick and painless as possible. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Moe" wrote in message ... I was kind of hoping not to have to purchase any software for this... Excel could do the job, but an access database would be so much better organized. -- Moe "Steve" wrote: I have assumed that your inventory items are consumable and periodically you purchase items to replenish your inventory. TblJob JobID JobNumber JobDescription Job Address fields TblItem ItemID ItemDesc QuantityOnHand TblItemToJob ItemToJobID JobID ItemToJobDate TblJobItem JobItemID ItemToJobID ItemID Quantity JobItemAssignedCost TblItemVendor ItemVendorID VendorName Vendor contact fields TblVendorItem VendorItemID ItemVendorID ItemID ItemCost TblItemPurchase ItemPurchaseID ItemVendorID PurchaseDate PurchaseOrderNumber TblItemPurchaseDetail ItemPurchaseDetailID ItemPurchaseID ItemID Quantity UnitCost If you need help, I can help you for a very reasonable fee. Contact me at my email address below. PC Datasheet Providing Customers A Resource For Help With Access, Excel And Word Applications "Moe" wrote in message ... What I need to do: I have some rather expensive inventory items that I need to keep track of. These are to be used in several projects (jobs). I'm trying to design a simple database to help me keep track of where everything goes, so I can bill the right job for the right products. More Details: Inventory items have an ID, and description. I need to know how many of each item I still have remaining. Jobs have unique ID numbers (I dont want to use autonumber for this). I was thinking maybe I could design something that would sort of do transactions. Assign a transaction ID (Autonumber is ok), A date, a project # (job#) and how many of each of the inventory items were transfered on that date, or transaction. I did a little designing, and came up with three tables. Inventory |_ ID |_ Description |_ Quatntity on hand (??) Jobs |_ ID |_ Address Transactions |_ ID (autonumber ok) |_ Date |_ Quantity |_ Description Can someone suggest an efficient relationships model to make this work? Thanks in advance -- Moe
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
