User Profile

Collapse

Profile Sidebar

Collapse
nkasaba
nkasaba
Last Activity: Jul 22 '10, 07:27 PM
Joined: May 17 '10
Location:
  •  
  • Time
  • Show
  • Source
Clear All
new posts

  • nkasaba
    replied to Search/Organization Recommendation
    Pat,

    That's a great idea! If I have anytime to work on this at home this weekend, I will try and let you know how it goes.

    As for tables, I made a TON. I learned on my first failed attempt at making this database that tables are awesome - as long as you don't use the damn lookup wizard!. I basically have 4 main tables - one for each form and sub-form all linked by 'Benchmark ID.' After that, I have a bunch of tables...
    See more | Go to post

    Leave a comment:


  • nkasaba
    replied to Search/Organization Recommendation
    Neo,

    This is why I did not just attach the database for you guys to dig through - I did not want to come off as trying to pawn off my work. I just need some idea as to where to begin. I have absolutely no idea where to start outside of some drawings I put down on paper....
    See more | Go to post

    Leave a comment:


  • nkasaba
    replied to Search/Organization Recommendation
    Pat,

    Thanks for the quick reply. You hit the nail right on the head in terms of different sub-forms. A fan motor is obviously going to require a different set of information than a radiator will.

    As for your second question, you are dead on again. The way I had imagined it (and tried to draw it) is basically a small table where when I click on Honda, I will see a list with every Honda part that has been tested, including...
    See more | Go to post

    Leave a comment:


  • nkasaba
    started a topic Search/Organization Recommendation

    Search/Organization Recommendation

    Since I'm unsure how to explain my situation in words, I took some screenshots to explain what I'm trying to do next. The purpose of this database is to store information about parts we will benchmark.


    This is the switchboard I have created thus far. None of the buttons do anything except the 'input part', which takes the user here...


    From here, the user will begin inputting vehicle/part information. Based...
    See more | Go to post

  • Yes absolutely. That's why I thought auto-numbering was the way to go. For example, I think have I have two Corvette ZR1 parts in there already - same car, two different parts (two different records as well). Because some cars can have 3 or 4 different engine options, I figured it was better to just give every car/part combo its own record.
    See more | Go to post

    Leave a comment:


  • Smiley,

    Thanks a TON for taking a look at it. I'm going to re-read your post when I get home and can open up the file and try to do everything you suggested.

    Purpose of this database: We will get a part into our office from a certain vehicle. This part may be a prototype part, our own part, etc. We want to put all of this information into a easy to organize database. Eventually, I'll work in reports (or just dump...
    See more | Go to post

    Leave a comment:


  • nkasaba
    started a topic [General] Database Design for a new Engineer

    [General] Database Design for a new Engineer

    Good afternoon everyone,

    My name is Nick and I am a fresh out-of-college Mechanical Engineer working for an automotive supplier. Unfortunately, my first task at my new job was to build a database to store information on our bench-marked parts. It's a small and simple project (and one that would probably take an experienced developer an hour), but I'm still pulling my hair out after a few days work! I am good with computers and the...
    See more | Go to post
No activity results to display
Show More
Working...