16:31
I think the main reason I am having a hard time is the examples that are out there are dealing with two or more separate tables. ie:the Category and Product combo box. If I only import the CodeKey33 spreadsheet, the info is in one table.... can relationships be created between columns and enable the data to be manipulated the way I would like? At this point I am so dazed and confused by the volume of information that is out there I don't dare try to wrap my head around the concatenating that Galaxiom suggested in the earlier post without a little more understanding.
If I import all 3 sheets, Code key 31, codekey32 and code key 33, how then do I relate the resulting tables. and there there is that little bit about the "group" code X0X where the middle digit identifies the group.
The bottom line... I am willing to pay for this help. I have a paypal account (or we can work out another method for payment delivery.)... lets work out a deal... maybe it could be an on going tutoring/ mentoring setup. I need help, which is why I am here to begin with. I do want to create this database, as it is the basis of my small business plan.
The attached excel workbook is showing how I received (some) the files from the ATA when I purchased the coding convention.
I would like to be able to import the tables from the excel file into access, in such a manner that I can create the appropriate relationships for the combo boxes to be able to act in the manner I described in my post above.
Do I import all 3 sheets, do I only import the components spread sheet? What columns of which sheet(s) should be imported. Once imported, how do I create the relationships that will let me use the info correctly in combo boxes, giving the level of detail wanted for reports??
Can this be done? If yes, would someone please be so kind as to walk me through how? For whatever reason I cannot reason or logic my way through this.... maybe it's because what I want to do can not be done!!
I did not design the VMR system.
I am attempting to incorporate the system into my database.
It was developed by the American Trucking Associations' Technology & Maintenance Council. (In my understanding 'normalized' to the nth degree)
A Structured Coding System
VMRS is a structured coding system, providing the discipline necessary to operate in
today's computer-based information age or — where desired — as a completely manual
system. Simple in concept, VMRS can be used at any level, from total operating systems
down to the individual part level. The level of coding used is entirely up to the user.
One can modify the coding level at any time without the need to redesign the coding
structure or implement costly new programs. No matter which level the user selects, the
data collected can be compared directly to data collected by others at the same or higher
VMRS coding level.
The coding structure encompasses most equipment found within today's transportation
activities including trucks, tractors, trailers, forklifts, shop equipment, off-road vehicles,
utility vehicles, etc.
Does the System Do the Following?
[*]Use the VMRS Vehicle Master Record.
[*]Identify Equipment Vocation -- Code Key 1.
[*]Segregate costs by Reason for Repair -- Code Key 14
[*]Identify work accomplished using VMRS Coding -- Code Key 15
[*]At minimum, identify systems via the three-digit VMRS System Code -- Code Key 31
[*]For more detail, identify assemblies via the three-digit VMRS Assembly Code -- Code Key 32
[*]For more detail, identify individual parts via the three-digit VMRS Component Code -- Code Key 33.
[*]Identify part/vehicle manufacturers, suppliers or brands universally using -- Code Key 34.
[*]Have the capability to record VMRS Technician Part Failure Codes -- Code Key 18.
VMRS System Level Codes
Code Key 31
VMRS 2000 uses a series of three-digit descriptor codes that readily and consistently
identify the specific systems involved. While these codes are the heart of the "common
language" of VMRS and are a vital part of the VMRS concept, they are by themselves
nothing more than coding conventions designed for use at all levels within the industry,
from fleets to mechanics to manufacturers to suppliers of parts. For example, brakes are
identified as a system by system code 013.
Assembly Level Codes
Code Key 32
Through the use of assembly level codes, VMRS provides additional capability to
further define Code Key 31's System Codes. The first classification below the system
level is referred to as the assembly. At this level, all major groupings within each system
are broken out and reported through the use of a three digit code. These, when used
with their system prefix, identify the specific assembly within a vehicle. For example,
front brakes and drums can be identified by a combination of the System and Assembly
Code 013-001.
Component Level Codes
Code Key 33
In order to provide a common generic term for each part within a vehicle, the system
and assembly codes are further subdivided to the component level. This is
accomplished through the use of an additional three digit part identifier code. These
codes should not be confused with the manufacturers' or suppliers' unique
identification (part) numbers, but rather should be considered universal identifiers or
generic terms for the part. For example, a front brake lining can be identified by the
following combination of System/Assembly/Component codes—013-001-015.
*(More info can be found in the link in my first post or here http://www.truckrealm.com/vmrs.htm )
!)
