Suggestions for a parts database?

R

Ricter

I'm looking for design ideas for a parts db that will provide the user with a
single, rapid data entry form and a single report, specifically a packing
list.

The attributes that make up a part line item for the packing list are:
Type (nut, bolt, pipe)
Size1 (5/8)
Size1unit (", for inches)
Size2 (7)
Size2unit (", for inches)
Pressure (150#)
Style (RF)
Material (SS)

Here are some examples of a full part description for the packing list report:
Nut, 5/8"
Bolt, 5/8" x 114 MM (mixed units)
Gasket, 2", 600#, RF, 304SS NON ASB

Problems:
Few parts have all attributes. Specifying a field to each attribute means
that some parts would require a precise number of "tabs" to the next relevent
field. To get around this, in my prototype, I just called them Att1, Att2,
etc., and concatenate them.

When I simply concatenate all these attributes, with a comma and space
between each, I get "weird" looking part descriptions, meaning there are
often too many commas and spaces between attributes.

Sometimes the unit is "MM", for millimeters.

The data entry form for this, as presently designed, really isn't much
faster than typing the entire part description out from left to right, which
is quite tedious and of course error-prone. This is true partly because the
size1 attribute, for example, may range from 1/8" to 12", in 1/8" increments,
so a dropdown here is quite long.

Any suggestions come to mind?

Thanks.
 
J

Jeff Boyce

Ricter

Don't know about some of the other facets, but the data entry of size1 might
also be handled by having the user enter:
[# of inches] and [# of 8th's]

Your form could look something like:

__ inches __/8ths

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
J

Joshua A. Booker

Ricter,

I have a feature called Part Builder in a purchasing solution for a
manufacturer. It allows very specific classification of parts with variable
numbers of attributes and generates IDs and descriptions.

You still have to setup the attributes but options for each attribute add on
the fly.

http://www.joshuabooker.com/Docs/PartBuilder.zip

Let me know if you have questions or want me to email it to you instead.

HTH,
Josh

Jeff Boyce said:
Ricter

Don't know about some of the other facets, but the data entry of size1 might
also be handled by having the user enter:
[# of inches] and [# of 8th's]

Your form could look something like:

__ inches __/8ths

Regards

Jeff Boyce
Microsoft Office/Access MVP


Ricter said:
I'm looking for design ideas for a parts db that will provide the user
with a
single, rapid data entry form and a single report, specifically a packing
list.

The attributes that make up a part line item for the packing list are:
Type (nut, bolt, pipe)
Size1 (5/8)
Size1unit (", for inches)
Size2 (7)
Size2unit (", for inches)
Pressure (150#)
Style (RF)
Material (SS)

Here are some examples of a full part description for the packing list
report:
Nut, 5/8"
Bolt, 5/8" x 114 MM (mixed units)
Gasket, 2", 600#, RF, 304SS NON ASB

Problems:
Few parts have all attributes. Specifying a field to each attribute means
that some parts would require a precise number of "tabs" to the next
relevent
field. To get around this, in my prototype, I just called them Att1,
Att2,
etc., and concatenate them.

When I simply concatenate all these attributes, with a comma and space
between each, I get "weird" looking part descriptions, meaning there are
often too many commas and spaces between attributes.

Sometimes the unit is "MM", for millimeters.

The data entry form for this, as presently designed, really isn't much
faster than typing the entire part description out from left to right,
which
is quite tedious and of course error-prone. This is true partly because
the
size1 attribute, for example, may range from 1/8" to 12", in 1/8"
increments,
so a dropdown here is quite long.

Any suggestions come to mind?

Thanks.
 
R

Ricter

Thank you all. Joshua, I dl'ed your app and will look at it this weekend,
thanks!

Joshua A. Booker said:
Ricter,

I have a feature called Part Builder in a purchasing solution for a
manufacturer. It allows very specific classification of parts with variable
numbers of attributes and generates IDs and descriptions.

You still have to setup the attributes but options for each attribute add on
the fly.

http://www.joshuabooker.com/Docs/PartBuilder.zip

Let me know if you have questions or want me to email it to you instead.

HTH,
Josh

Jeff Boyce said:
Ricter

Don't know about some of the other facets, but the data entry of size1 might
also be handled by having the user enter:
[# of inches] and [# of 8th's]

Your form could look something like:

__ inches __/8ths

Regards

Jeff Boyce
Microsoft Office/Access MVP


Ricter said:
I'm looking for design ideas for a parts db that will provide the user
with a
single, rapid data entry form and a single report, specifically a packing
list.

The attributes that make up a part line item for the packing list are:
Type (nut, bolt, pipe)
Size1 (5/8)
Size1unit (", for inches)
Size2 (7)
Size2unit (", for inches)
Pressure (150#)
Style (RF)
Material (SS)

Here are some examples of a full part description for the packing list
report:
Nut, 5/8"
Bolt, 5/8" x 114 MM (mixed units)
Gasket, 2", 600#, RF, 304SS NON ASB

Problems:
Few parts have all attributes. Specifying a field to each attribute means
that some parts would require a precise number of "tabs" to the next
relevent
field. To get around this, in my prototype, I just called them Att1,
Att2,
etc., and concatenate them.

When I simply concatenate all these attributes, with a comma and space
between each, I get "weird" looking part descriptions, meaning there are
often too many commas and spaces between attributes.

Sometimes the unit is "MM", for millimeters.

The data entry form for this, as presently designed, really isn't much
faster than typing the entire part description out from left to right,
which
is quite tedious and of course error-prone. This is true partly because
the
size1 attribute, for example, may range from 1/8" to 12", in 1/8"
increments,
so a dropdown here is quite long.

Any suggestions come to mind?

Thanks.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top