Same Name, Different Use

[Seahawk via AccessMonster.com]

Hello to everyone! New to the community, but from everything I have read in
here you guys are amazing.
Self taught Access user here so please bear with me if I get confused myself.

I have a db that has all our parts listed in a table 'Parts'. The parts are
listed as: (Name of Part) (Machine Used On)\same field, probably my first
mistake. So lets say: Screw Plastic Frame. Screw being Name of Part and
Plastic Frame being Machine Used On.

My question is: Is it possible to create a query that will only pull up the
name of the parts that are used on a specific machine as they are listed? Or
do I have to seperate these two?

 

[ra.john]

No you cant with the data stored in that format, you would need to
split the two fields-
Part and Machine.

 

[Seahawk via AccessMonster.com]

Thank you for the response. I kinda figured that, but thought I would check
first.

 

[John Vinson]

Hello to everyone! New to the community, but from everything I have read in
here you guys are amazing.
Self taught Access user here so please bear with me if I get confused myself.

I have a db that has all our parts listed in a table 'Parts'. The parts are
listed as: (Name of Part) (Machine Used On)\same field, probably my first
mistake. So lets say: Screw Plastic Frame. Screw being Name of Part and
Plastic Frame being Machine Used On.

My question is: Is it possible to create a query that will only pull up the
name of the parts that are used on a specific machine as they are listed? Or
do I have to seperate these two?

Well... sort of. You can use a query criterion of

LIKE "*Plastic Frame"

to find all records for which "Plastic Frame" is the final string of
the composite field. If you have machine used on values of "Plastic
Frame" and "Deluxe Plastic Frame" you'll see them mixed.

You do indeed need two fields; it's a basic principle that fields
should be "atomic", having only one piece of information.

John W. Vinson[MVP]