<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Please, please help? :/ How to do this in MS Access?</title>
	<atom:link href="http://www.freshbatchsoap.com/please-please-help-how-to-do-this-in-ms-access/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.freshbatchsoap.com/please-please-help-how-to-do-this-in-ms-access/</link>
	<description>Soap</description>
	<lastBuildDate>Sat, 31 Jul 2010 07:31:48 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: emdex</title>
		<link>http://www.freshbatchsoap.com/please-please-help-how-to-do-this-in-ms-access/comment-page-1/#comment-10224</link>
		<dc:creator>emdex</dc:creator>
		<pubDate>Mon, 08 Feb 2010 04:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.thebasketbee.com/please-please-help-how-to-do-this-in-ms-access/#comment-10224</guid>
		<description>My suggestion would be to create a one to many relationship in the relationship window
One customer to many orders
So you would have your form with the customer and a subform for all their orders</description>
		<content:encoded><![CDATA[<p>My suggestion would be to create a one to many relationship in the relationship window<br />
One customer to many orders<br />
So you would have your form with the customer and a subform for all their orders</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colanth</title>
		<link>http://www.freshbatchsoap.com/please-please-help-how-to-do-this-in-ms-access/comment-page-1/#comment-10225</link>
		<dc:creator>Colanth</dc:creator>
		<pubDate>Mon, 08 Feb 2010 04:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.thebasketbee.com/please-please-help-how-to-do-this-in-ms-access/#comment-10225</guid>
		<description>Start over.  A hamper has a hamper ID.

In the contents table you have an entry for each for each item&#039;s ID (a standard hamper would be an item) in that particular hamper ID.

You have a table of standard hampers and their prices.

You have a table of content items and their prices (and ID numbers).

You have a customer table - name, address, charge card info, if you want to keep it.  And a customer ID.

An order table - customer ID, hamperID, date of order, date picked up, amount paid (if one payment for 3 hampers, each order will get the full payment).  And order ID, of course.

A payment table - date, method of payment, amount of payment, hamperID the payment is for (if one payment is made for 3 hampers, this entry gets the payment for the hamper it&#039;s paying for).  And paymentID.  This table also gets updated if an order is returned - the payment is negative.

Cost (of a hamper, of an order) is calculated when needed - you don&#039;t keep data in the database that can be calculated.  You calculate it when a payment is made (to print the receipt, showing the balance still due, or a zero balance), when an order is placed (to create the receipt showing the price), etc.

You also have all the data you need for your ledger and accounts receivable programs (and inventory and ordering).</description>
		<content:encoded><![CDATA[<p>Start over.  A hamper has a hamper ID.</p>
<p>In the contents table you have an entry for each for each item&#8217;s ID (a standard hamper would be an item) in that particular hamper ID.</p>
<p>You have a table of standard hampers and their prices.</p>
<p>You have a table of content items and their prices (and ID numbers).</p>
<p>You have a customer table &#8211; name, address, charge card info, if you want to keep it.  And a customer ID.</p>
<p>An order table &#8211; customer ID, hamperID, date of order, date picked up, amount paid (if one payment for 3 hampers, each order will get the full payment).  And order ID, of course.</p>
<p>A payment table &#8211; date, method of payment, amount of payment, hamperID the payment is for (if one payment is made for 3 hampers, this entry gets the payment for the hamper it&#8217;s paying for).  And paymentID.  This table also gets updated if an order is returned &#8211; the payment is negative.</p>
<p>Cost (of a hamper, of an order) is calculated when needed &#8211; you don&#8217;t keep data in the database that can be calculated.  You calculate it when a payment is made (to print the receipt, showing the balance still due, or a zero balance), when an order is placed (to create the receipt showing the price), etc.</p>
<p>You also have all the data you need for your ledger and accounts receivable programs (and inventory and ordering).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
