Data Type Mismatch expression

[nick243]

I have narrowed it down to BRI Locations A query that is causing Data type mismatch in criteria. That I believe has to do with the line expression in the BRI A Locations. I provided the 2 tables that are in the relationship. I cannot find where this datatype mismatch is going on. Thank you for any help in salving this.

[nick243]

TestDatabase.mdb
I forgot to add the file.

[aytee111]

"Line" is a reserved word, change it to something else.

[RuralGuy]

Look at the last element of the Line: definition in the query.

[nick243]

Ok, I see the last element does not have outstations around the 6 because it is a text field. Just add the quotations correct?

[nick243]

Thank you so much it worked.

[RuralGuy]

YES. I tried it and the error goes away.

[aytee111]

Interesting. RuralGuy, I see you are on 2013 as well yet we got different results. Weird.

[RuralGuy]

@aytee111 - What results did you get?

[aytee111]

All I did was change the name of the field and it worked!

[RuralGuy]

Hmm...The last element of the query was comparing a String to a number and should have thrown the error reported. Maybe it is the difference between 64bit and 32bit Access. Interesting.

[nick243]

I was trying to stay away from changing the name of the field because it would cause a chain reaction for so many queries. This query is part of a much bigger chain. Thank you for the help.

[RuralGuy]

attee111 has a valid point and reserved words should be avoided or they may bite you in the butt later.
Here's a good reference for Reserved Words: http://www.allenbrowne.com/AppIssueBadWord.html#A

[nick243]

Thank you for the reference sheet. This database was created well before me. I will try to keep this in mind in the future.