Query Design Changes Not Saving

[ItsRoland]

I'm trying to add a field to a query that I made a while ago. Every time I add the field I save the changes and close the query, but when I reopen the query the field I added is no longer there.



As far as I'm aware, I can save changes to everything else in the database like normal. I tested this on a number of other queries/forms and haven't seen the issue occur anywhere other than the query in question.

Closing the query and clicking 'yes' on the save changes prompt provides no different outcome from saving via right click -> save.
I've tried compact and repair, but the issue persists.
There is no one else accessing the database, I read that this might cause the issue while I was looking for an answer.

I wasn't able to find much helpful information on this when I was searching for an answer, so hopefully someone here knows how to fix it.

If any additional information is needed, please let me know. Thanks in advance for any help!

[June7]

No idea. Would have to review the database. If you want to provide, follow instructions at bottom of my post.

[ItsRoland]

AssetInv1.8 - Changes - Copy.zip

Above is the database. The query in question is 'qryNetworks', and I'm trying to add the 'ID' field from 'tblNetworks' to it.

While prepping to attach the database I discovered that if I leave the 'shown' checkbox checked for the field it'll save properly, but if I set it to not be shown it will no longer be in the query after closing and reopening. Even if the field was listed as shown and saved properly as being a part of the query, it completely goes away after you stop showing it and close the query.

Not sure if this new information changes anything. I can always just leave the field as shown, but I would prefer if that wasn't the case and don't want this issue to pop up again somewhere that this compromise doesn't work/isn't an option.

Thanks again for the help!

[June7]

That is normal behavior. Can't have field as 'not shown' unless it has filter or sort criteria.

[isladogs]

Whilst it is indeed normal behaviour, you can circumvent it by using Like '*' in the criteria row.
However I really can't see the point myself