|
| 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
May 3rd, 2004, 10:41 PM
|
|||
|
|||
Personalised Customer Orders
I am selling personalised gifts on the Web (very small time but hopefully growing). Using FrontPage and Access 2000, I have managed to create ASP pages to collect the customer's details as well as the the personalisation details for the products. The customer can, and usually does, order many items - all with different personalisation i.e. two mugs with the names Janet and John printed on them and one t-shirt with Mary printed on it. To avoid the customer having to enter their details over and over again both the Customer and the Order tables are separate to each other. The customer usually comes back to order more items later in the year.
I am able to retrieve the information from both tables, but for the life of me I cannot marry them up. Because the business is so small I can usually work out who has ordered what by looking at the time the orders were received........yes, really!!! Can anybody offer a possible solution to the problem whereby I can tie-in personalised orders to a customer. I am not a programmer - just an enthusiast with a copy of "Running Microsoft Access 2000". I could even be persuaded to adapt the Access 2000 sample database "Order Entry" to fit my needs if that helps. Many thanks in anticipation Neill 
|
|
#2
May 4th, 2004, 03:29 AM
|
|||
|
|||
|
Personalised Customer Orders
You should have a seperate table for: Customers Details,
Products, Orders, and possibly another of Order Details/Personalisation. Each Table should inclued a Colum Defined as Primary Key (uniquely identifies record). You then need to create relationships between the tables. In the Orders table create a field Customer. Create a relate a relationship between this field and the Primary Key field in Customers table. (You can do this by selecting Lookup Wizard in the Data type property). Repeat this to relate your tables. -----Original Message----- I am selling personalised gifts on the Web (very small time but hopefully growing). Using FrontPage and Access 2000, I have managed to create ASP pages to collect the customer's details as well as the the personalisation details for the products. The customer can, and usually does, order many items - all with different personalisation i.e. two mugs with the names Janet and John printed on them and one t-shirt with Mary printed on it. To avoid the customer having to enter their details over and over again both the Customer and the Order tables are separate to each other. The customer usually comes back to order more items later in the year. I am able to retrieve the information from both tables, but for the life of me I cannot marry them up. Because the business is so small I can usually work out who has ordered what by looking at the time the orders were received........yes, really!!! Can anybody offer a possible solution to the problem whereby I can tie-in personalised orders to a customer. I am not a programmer - just an enthusiast with a copy of "Running Microsoft Access 2000". I could even be persuaded to adapt the Access 2000 sample database "Order Entry" to fit my needs if that helps. Many thanks in anticipation Neill .
|
|
#3
May 4th, 2004, 07:43 AM
|
|||
|
|||
|
Personalised Customer Orders
hi Neill, suggest you read the following link before using the Lookup Wizard
in any of your table fields. http://www.mvps.org/access/lookupfields.htm btw, while you're there, look around. the MVPs (of which i am *not* one) constitute the larger portion of the brain power in the newsgroups and their site has a great deal to offer. for starters, suggest you also read the following http://www.mvps.org/access/tencommandments.htm hth wrote in message ... You should have a seperate table for: Customers Details, Products, Orders, and possibly another of Order Details/Personalisation. Each Table should inclued a Colum Defined as Primary Key (uniquely identifies record). You then need to create relationships between the tables. In the Orders table create a field Customer. Create a relate a relationship between this field and the Primary Key field in Customers table. (You can do this by selecting Lookup Wizard in the Data type property). Repeat this to relate your tables. -----Original Message----- I am selling personalised gifts on the Web (very small time but hopefully growing). Using FrontPage and Access 2000, I have managed to create ASP pages to collect the customer's details as well as the the personalisation details for the products. The customer can, and usually does, order many items - all with different personalisation i.e. two mugs with the names Janet and John printed on them and one t-shirt with Mary printed on it. To avoid the customer having to enter their details over and over again both the Customer and the Order tables are separate to each other. The customer usually comes back to order more items later in the year. I am able to retrieve the information from both tables, but for the life of me I cannot marry them up. Because the business is so small I can usually work out who has ordered what by looking at the time the orders were received........yes, really!!! Can anybody offer a possible solution to the problem whereby I can tie-in personalised orders to a customer. I am not a programmer - just an enthusiast with a copy of "Running Microsoft Access 2000". I could even be persuaded to adapt the Access 2000 sample database "Order Entry" to fit my needs if that helps. Many thanks in anticipation Neill .
|
|
#4
May 4th, 2004, 06:40 PM
|
|||
|
|||
|
Personalised Customer Orders
Thanks for the plug, Tina. g
-- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm "tina" wrote in message ... hi Neill, suggest you read the following link before using the Lookup Wizard in any of your table fields. http://www.mvps.org/access/lookupfields.htm btw, while you're there, look around. the MVPs (of which i am *not* one) constitute the larger portion of the brain power in the newsgroups and their site has a great deal to offer. for starters, suggest you also read the following http://www.mvps.org/access/tencommandments.htm hth wrote in message ... You should have a seperate table for: Customers Details, Products, Orders, and possibly another of Order Details/Personalisation. Each Table should inclued a Colum Defined as Primary Key (uniquely identifies record). You then need to create relationships between the tables. In the Orders table create a field Customer. Create a relate a relationship between this field and the Primary Key field in Customers table. (You can do this by selecting Lookup Wizard in the Data type property). Repeat this to relate your tables. -----Original Message----- I am selling personalised gifts on the Web (very small time but hopefully growing). Using FrontPage and Access 2000, I have managed to create ASP pages to collect the customer's details as well as the the personalisation details for the products. The customer can, and usually does, order many items - all with different personalisation i.e. two mugs with the names Janet and John printed on them and one t-shirt with Mary printed on it. To avoid the customer having to enter their details over and over again both the Customer and the Order tables are separate to each other. The customer usually comes back to order more items later in the year. I am able to retrieve the information from both tables, but for the life of me I cannot marry them up. Because the business is so small I can usually work out who has ordered what by looking at the time the orders were received........yes, really!!! Can anybody offer a possible solution to the problem whereby I can tie-in personalised orders to a customer. I am not a programmer - just an enthusiast with a copy of "Running Microsoft Access 2000". I could even be persuaded to adapt the Access 2000 sample database "Order Entry" to fit my needs if that helps. Many thanks in anticipation Neill .
|
|
#5
May 4th, 2004, 07:53 PM
|
|||
|
|||
|
Personalised Customer Orders
have to earn that advertizing fee y'all paid me. bow and smile
"Lynn Trapp" wrote in message ... Thanks for the plug, Tina. g -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm "tina" wrote in message ... hi Neill, suggest you read the following link before using the Lookup Wizard in any of your table fields. http://www.mvps.org/access/lookupfields.htm btw, while you're there, look around. the MVPs (of which i am *not* one) constitute the larger portion of the brain power in the newsgroups and their site has a great deal to offer. for starters, suggest you also read the following http://www.mvps.org/access/tencommandments.htm hth wrote in message ... You should have a seperate table for: Customers Details, Products, Orders, and possibly another of Order Details/Personalisation. Each Table should inclued a Colum Defined as Primary Key (uniquely identifies record). You then need to create relationships between the tables. In the Orders table create a field Customer. Create a relate a relationship between this field and the Primary Key field in Customers table. (You can do this by selecting Lookup Wizard in the Data type property). Repeat this to relate your tables. -----Original Message----- I am selling personalised gifts on the Web (very small time but hopefully growing). Using FrontPage and Access 2000, I have managed to create ASP pages to collect the customer's details as well as the the personalisation details for the products. The customer can, and usually does, order many items - all with different personalisation i.e. two mugs with the names Janet and John printed on them and one t-shirt with Mary printed on it. To avoid the customer having to enter their details over and over again both the Customer and the Order tables are separate to each other. The customer usually comes back to order more items later in the year. I am able to retrieve the information from both tables, but for the life of me I cannot marry them up. Because the business is so small I can usually work out who has ordered what by looking at the time the orders were received........yes, really!!! Can anybody offer a possible solution to the problem whereby I can tie-in personalised orders to a customer. I am not a programmer - just an enthusiast with a copy of "Running Microsoft Access 2000". I could even be persuaded to adapt the Access 2000 sample database "Order Entry" to fit my needs if that helps. Many thanks in anticipation Neill .
|
|
#6
May 4th, 2004, 09:56 PM
|
|||
|
|||
|
Personalised Customer Orders
Many thanks for your help and advice - much appreciated. I'm still trying to get my head around the basics of relational databases - perhaps it will hit me one day :-)
|
|
#7
May 4th, 2004, 10:52 PM
|
|||
|
|||
|
Personalised Customer Orders
The check for the next installment is in the mail, young lady.
-- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm "tina" wrote in message ... have to earn that advertizing fee y'all paid me. bow and smile "Lynn Trapp" wrote in message ... Thanks for the plug, Tina. g -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm "tina" wrote in message ... hi Neill, suggest you read the following link before using the Lookup Wizard in any of your table fields. http://www.mvps.org/access/lookupfields.htm btw, while you're there, look around. the MVPs (of which i am *not* one) constitute the larger portion of the brain power in the newsgroups and their site has a great deal to offer. for starters, suggest you also read the following http://www.mvps.org/access/tencommandments.htm hth wrote in message ... You should have a seperate table for: Customers Details, Products, Orders, and possibly another of Order Details/Personalisation. Each Table should inclued a Colum Defined as Primary Key (uniquely identifies record). You then need to create relationships between the tables. In the Orders table create a field Customer. Create a relate a relationship between this field and the Primary Key field in Customers table. (You can do this by selecting Lookup Wizard in the Data type property). Repeat this to relate your tables. -----Original Message----- I am selling personalised gifts on the Web (very small time but hopefully growing). Using FrontPage and Access 2000, I have managed to create ASP pages to collect the customer's details as well as the the personalisation details for the products. The customer can, and usually does, order many items - all with different personalisation i.e. two mugs with the names Janet and John printed on them and one t-shirt with Mary printed on it. To avoid the customer having to enter their details over and over again both the Customer and the Order tables are separate to each other. The customer usually comes back to order more items later in the year. I am able to retrieve the information from both tables, but for the life of me I cannot marry them up. Because the business is so small I can usually work out who has ordered what by looking at the time the orders were received........yes, really!!! Can anybody offer a possible solution to the problem whereby I can tie-in personalised orders to a customer. I am not a programmer - just an enthusiast with a copy of "Running Microsoft Access 2000". I could even be persuaded to adapt the Access 2000 sample database "Order Entry" to fit my needs if that helps. Many thanks in anticipation Neill .
|
|
#8
May 5th, 2004, 02:01 AM
|
|||
|
|||
|
Personalised Customer Orders
the best way to get good at building databases is to build databases
(hopefully not mission-critical ones g). keep building and researching and reading and asking questions and solving those real-world problems that come up - it *will* get easier, quicker and a lot more fun! good luck! "Neill" wrote in message ... Many thanks for your help and advice - much appreciated. I'm still trying to get my head around the basics of relational databases - perhaps it will hit me one day :-)
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
