Ever think you'd hear me say that? :iroll:
Does anyone have Microsoft Access...and know how to use it?
I have made practice db files, I've looked at the examples, and I've even spent money on "for dummies" books. I cannot get this thing to do what I want.
I need a customer database for the tannery, where, in the form version, I can either add a customer or add an order to a customer...and also be able to look up past orders from a customer...along with thier status.
I have all the data, and can do the inserting, building the blank database is kicking my :shck:
My Ex is a programmer, she did one for me years ago in about 10 minutes.......yeah that aggrevates me :laf: but it left when she did. :eyebrownod:
Well Iam here with Nellie Mae and she told me not to tell you how to do it. I would tell you anyway BUT after makin fun of my 3 teeth it ain't hapinin :roflmao:
Fell right into that one didn't I? :laf:
Quote from: FinsnFur on January 01, 2007, 07:14:12 PM
Fell right into that one didn't I? :laf:
You didn't just say that???? :hahaha: :hahaha: YOU DID!!!!!!
:roflmao: :roflmao: :roflmao: :roflmao: :roflmao: :roflmao: :roflmao: :roflmao: :roflmao: :roflmao: :roflmao:
Jim,
Ask that question over again in English and I'll see if I can help you out. :wo:
Your kiddin me?
Microsoft Access for making databases.
You build tables, give each one a primary key etc.
Then queries if your going to use any.
Then establish table relationships, such as customer vs orders, etc.
Then the form, what you see when you open it. Which I was trying to get a small text field where I enter a customer name. If the customer is in the database, it shows me his orders below that in another field, a description and their status, and lets me add an order to him if need be.
If the customer's name isn't in the database, it accepts it and lets me add an order to it.
Building the tables was easy, the query part tripped me, and the form section gutted me. :sad:
I can't figure out if I need a linking table to link the two tables or what. I can't imagine why I would because I might have one customer linked to many orders, but I would never have one order linked to many customers...which would indicate a many to many situation, supposedly the only time you need a linking table.
:shrug:
Damn Jim... You know I was just kidding! All I know about the computer is how to turn it on and then how to talk smart
I figured, but being in the business that you are..... I saw a dim light of hope :eyebrownod:
Sorry about the delayed response ... I use Microsoft access for my customers.
What all do you need help with?
Email me: oktrap1@cox.net
Your a knight :biggrin:
Lots of things Reggy.
Is it necessary to have two separate tables regarding orders? Say, one for orders and one for order details like some of the examples show?
Do I have to know programming to set up a usefull query? Cuz I can't seem to figure it out?
And all my attempts at forms so far turn out to be nothing but every field from every table :shrug: