Oh, right. No worries.

If the field can never be a float, isn't there a way to set the type in the CREATE TABLE statement to enforce that, so that LabKey will know it is really an INT column?

Well, the field can be float, in that it's theoretically possible. I'm saying that it would never be the case. In previous roles, I have always specified number columns as 'number' (data type) - whether they be floats or int's. I imagine its a common practice. I don't think its exactly a possibility for me to go changing the datatypes of tables.

OK. I think I saw somewhere that it loads in tables and views. So im going to try creating a view, casting number fields to int's and see if that solves the problem. (just gotta wait for that priv before i can test)