Question building a database (Open Office Base), table creation, etc.
Discuss Question building a database (Open Office Base), table creation, etc. in the SQL Development forum on ASP Free. Question building a database (Open Office Base), table creation, etc. SQL forums discussing structured query language related questions that are platform independent. Discussions include advanced topics such as joins, stored procedures, and triggers.
ASP Free and Iron Speed Designer are giving away $5,500+ in FREE licenses. Iron Speed's RAD CASE toolset can save up to 80% of your coding time. One free license per week, one perpetual license per month!
Receive the tools necessary to be the rock star of your field. Our 12-month program teaches you the evolving world of multi-channel marketing as well as the complex issues and opportunities found in the industry.
Web development can be a daunting task, even for specialists. There is a lot of information to absorb and a lot of technologies to learn in order to manage a superior website. When trying to learn the ropes, developers need a reliable source to introduce new ideas that can be easily implemented. When working on large projects, even web veterans may run into a technology or an aspect of a technology that they are unfamiliar with.
Posts: 334
Time spent in forums: 5 Days 11 h 47 m 16 sec
Reputation Power: 179
Question building a database (Open Office Base), table creation, etc.
Okay, I am learning (again) databases, this time with ooBase, the database app in Open Office.
I am currently building a UML-type design framework for a maintenance tracking database for a unit that I work on.
Each aircraft has two of these units. They receive signals from the airport and use those signals to tell the aircrew the direct bearing to the airport, whether they are flying toward or away from it, and gives flight-path directions on approach.
The units, when they fail, are sent to my shop for repair. I check the unit for revisions (one SB is now required to be installed, which is why I am going to track them all with this database), and run a diagnostic program on the unit. The diagnostic needs to know what SBs are installed so that it will test the unit properly.
When it fails a step, I have to repair it, either by making adjustments or troubleshooting down to one or more bad components and replacing them.
After replacing certain components, I may have to make adjustments or even align the entire unit.
Sometimes a unit is pulled for troubleshooting purposes, or there was something else wrong with the aircraft and replacing the unit did not fix the plane. In those cases, I will either have no repair action, or I will have a service bulletin to install but that had nothing to do with the original discrepancy, and I would like to track those actions separately.
Certain circuit card part numbers are installed or modified with certain service bulletins, so I want to be able to use conditional statements on my data entry to keep from misentering configuration data (or catch a unit that is misconfigured). Also, different cards require different calibration procedures (for instance, an A2 card P/N 662-6652-007 requires special equipment that a -004 doesn't need) so I might have a need to track those units which require special handling or perhaps arrange to get one-off units installed in a plane we are selling.
In the initial setup, I had a single table (the UML design has exploded into ten tables with more to come) which tracks each unit by Part Number and Serial Number (same unit, but three different part numbers with minor differences).
I though I should use a set of Boolean entities in a standalone table that lists each of 25 Service Bulletins then use the primary key from that table (one unique key for each unique combination of SBs installed) in a linking table to track what bulletins are on each unit (on average, each unit will have ten of the nineteen SBs currently out).
Ultimately, through this database, I will be tracking more than 500 units and be able to identify which ones have what SBs on them, and the part numbers of each of the six sub-assemblies, as well as a history of repairs.
I have already started writing an SQL script to build the appropriate databases, if that helps you understand what I am trying to do.
My primary question is: How do I set up a form or whatever that will allow me to enter the 25 service bulletins for a unit and be able to generate (or identify as already existing in the SB table) a unique key for the main tracking table?
In other words, I know a lot of the units will have SBs 1-9, 11-19 installed, and it would be simpler (in the long run) if I can punch in the checkboxes and the database will say, 'oh, that's unique key 001' and so when I run a query, theoretically, it could expand that one column entry '001' into a list of the SBs installed (ie 1-9,11-19).
Does that make any sense? Anyway, if someone could point me in the right direction, I would appreciate the help.
__________________ Almost Ancient Folding Wizard
For difficult hardware problems, go to the Hard Side™-- DevHardware Forums
Posts: 334
Time spent in forums: 5 Days 11 h 47 m 16 sec
Reputation Power: 179
Hrm... could I make all 25 of the boolean columns part of the primary key? It would solve my problem of making sure there were no duplicates, but it isn't exactly elegant.
Posts: 334
Time spent in forums: 5 Days 11 h 47 m 16 sec
Reputation Power: 179
Okay, so the problem was (with the composite key) that I needed to format the constraint for the foreign key the same way as the original composite primary key:
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
