Customer Information/Service Request Database

[mbailey]

I am trying to create a database where customers would enter their information and then write a description of the service they are requesting. As of now, I have one form created where the customer would enter their information and submit, then that information is stored in a table called "Customer Info". The primary key of this table will be used as the unique ID for each customer. I want to create a second form that would have a drop down menu (combo box?) where the customer would find and select their name, then write a description in a "Request" field of the computer service they are needing. When they submit this request, it would be saved into a second table called "Requests" and each request would be associated to the customer by their ID number. My first form works fine, however I cant get the second form to work. On the second form I have created, when the customer name is selected from the combo box, I would like it to associate the issue they describe with their customer ID number, pulled from the Customer Info table. I feel like I should have a One-to-Many relationship between the customer ID number on the first table and something in the Requests table, but I can't figure that out. When I put the fields into the second form, it wouldn't pull the customer ID number when the customer name was selected and also wouldn't allow me to type in the "Request" field. I'm not sure whats going wrong and hopefully this isn't too confusing, but any help would be appreciated. If anything needs clarifying, please let me know.



Thanks.

P.S. Eventually when I get these two forms to work, I need to have a third form where I would be able to select any customer and then see all their information from the Customer Info table and also have all the service requests associated to their ID number be shown.

[June7]

Why would you allow customer the ability to select any customer ID from a combobox and view anyone's records?

Consider a form/subform arrangement: http://office.microsoft.com/en-us/ac...010098674.aspx

Suggest a customer login then the data entry/edit/view forms could have filtering criteria to show only that customer's records. No need to pick from a combobox.

Is this a web database?

[mbailey]

The customer wouldn't be able to see other customers records. On the form where they enter their service requests there are only two fields: one to select their name and one to enter their request. The form where all the customer information would be shown would not be accessible by the customers. One of my main problems is getting the service request form to pull the customer ID when they select their name from the combo box. And no its not a web database, I will create an ACCDE file that will only allow the customer to view what they need to see and it will be placed on a computer in the waiting room/lobby. The form/subform arrangement would be good for showing the customers entire record.

[orange]

I think you should step back and tell us the scope of your proposed application. The old who, what, where, when, how and how much type of thing so we can get some feel for what you are trying to do.

Who will be the users? Who are they requesting Services from? You should be identifying some business rules/facts in order to identify your tables and relationships.

Is this like an Angies' List or something between you and some customers?
I worked on a Company/Products/Services database involving Canadian Companies.
Here are sample links for 2 random companies
http://www.ic.gc.ca/app/ccc/srch/nvg...=1921&app=sold

http://www.ic.gc.ca/app/ccc/srch/nvg...000&profileId=
Good luck.

[June7]

If they select their name from a combobox, what is to prevent them selecting someone else's name/ID?

[mbailey]

Sorry for not replying for so long, I've been out of town. So a little background, I am trying to create this database for my grandfather's computer repair/networking business. Right now, he is just using paper forms and filing them in a cabinet to keep all his customer records (e.g. their usernames, passwords, etc) and would like a database to manage this information better. My plan for creating this database was as follows:

1) The first form the database would open up to would have two buttons: New Customer and Returning Customer
2) If they select new customer, a new form will open and they will enter their information (name, address, phone numbers, operating system, username, password, etc), then they click submit
3) Once they click submit, or if they click returning customer, another form opens and on this form there are only two fields: the combobox where they will select their name, and a text box where they will type a description of what they are needing done (virus removal, reformatting, etc).
--- Yes they would be able to select someone else's name/ID, but they would not be able to see any of that customers' personal information, so there won't be any privacy issues or anything like that.
4) Once the customer has written their service request, they would submit that form and everything would close and go back to step 1.

There will also be buttons in the database that would allow my grandfather to open a search form or something like that where he could select a customers name and all their information would populate existing fields on that form and underneath there would be a record of every service request that is connected to that particular customers' ID. This button will be protected with a password so that the customers could not access this form.

I already have the first and second steps working. I am having difficulty getting the form where they would write their service request to work and getting it to associate the request with whichever customer is selected in the combobox. Hopefully this clears up some questions and provides more helpful information to help me get this working. If I need to explain anything further, just let me know.

Thanks.

[June7]

Options:

1. form/subform arrangement
Main form would be the one with unbound combobox for selecting customer, form RecordSource SELECT CustomerID FROM Customers;
Code would filter the main form to the CustomerID record.
Subform would be the service request form, linked to main form by CustomerID fields.

2. code to pass CustomerID to the service request form