Number range restriction

[jlindquist23]

I have a database that kicks back a message if you enter a number higher than 55.
I need to change the range to a higher number but can't figure out how it was programmed.


There isn't a limit/range set in the query or in the table for that variable.
I've looked through the code to find it and no luck.

Can someone think of where else it would be?
Thank you!!

[Welshgasman]

Not really.
Why not upload the DB?

[davegri]

Might be here in table design:

[Micron]

There sees to be 2 properties missing from that table design pic?
Odd that Single is being used for a field that would have a max value of 2 digits (unless decimal places are required, I guess). The validation is probably in the form code.
@jlindquist23; do you tend to struggle with getting info in/out of this db? I ask because it's fairly obvious that it's not normalized.

[jlindquist23]

Thanks for the suggestion! I went and looked and those are blank.

[davegri]

There sees to be 2 properties missing from that table design pic?

@Micron, I see that now, too. And I learned something. The table design view is affected by options:

[jlindquist23]

They do use a one place decimal.
I'm not sure what "normalized" means.

[Micron]

@davegri; Isn't that for the little 'button' (looks like the little error checking flag) for updating all where the field is used? IIRC, you deselect that option and you don't get prompted if you change a field from integer to long for example? In your pic it looks like you chose a text field as opposed to a number type field so some options certainly would not apply to one or the other.

[jlindquist23]

Everything in the database works great!
I just can't remember how the number entry was restricted. I know that the entry can't be above 57.
The validation rule and text are blank.

[Micron]

They do use a one place decimal.
I'm not sure what "normalized" means.

You appear to have repeating fields (fields with very similar names distinguished by some characteristic - often by appending numbers).

A table is for an entity, the fields are for its attributes, so I'm not saying the table or db lacks normalization for sure because I don't know what the entity is or what its attributes are. Just going by the similar names here. Ask Google about db normalization if you don't know what it is. You might find it to be a challenging concept to fully grasp - it's not a breeze for most people, I think.

[Micron]

Everything in the database works great!
I just can't remember how the number entry was restricted. I know that the entry can't be above 57.
The validation rule and text are blank.

Then it's probably code behind the form as I mentioned. You'd have to put it into design view and open vb editor if it's not restricted (Ctrl+G) and look at update event code. Or post zipped db copy. Could also be Form_BeforeInsert code.

[Welshgasman]

Is there a Settings table even?, where that limit is set?

[CJ_London]

Bit confused - you are suggesting the limit applies to Centre Grind (at least that is what your images show and you haven't actually stated which field you are concerned about). But the message is about hardness which would appear to be another field. Perhaps you are looking at the wrong field?

[jlindquist23]

The database is split and has a back end to it.
I didn't realize that you couldn't see the validation rules when looking at the table from the front end of the database.
Thanks everyone for your help!

[Welshgasman]

Why not mark it solved in the Thread Tools?
That way people can see immediately?

Edit: I can see Validation rules fine from my FE ?