Access randomly asks me for a data value that no longer exists

[blackwolf23]

My main table which leads to all the other tables had a variable which I deleted. It was of no significant importance it was more there for a visual improvement of the table. Now that I deleted it most forms and queries keep asking for its value.Even if i put in blank it still works.How do i fix this ' . Is there a way for me to manually hide that message ?

 

[CJ_London]

sounds like you are still referencing it somewhere - perhaps in the filter or sort properties of the form? Or maybe in a combo or listbox rowsource/referenced query or controlsource of a control

 

[blackwolf23]

sounds like you are still referencing it somewhere - perhaps in the filter or sort properties of the form? Or maybe in a combo or listbox rowsource/referenced query or controlsource of a control

Yeah.. It seems to be referenced at the add existing field tabs. Is there a way to referesh that tab so the variable dissapiers or do I have to make the whole form all over again

 

[Tieval]

It is only referenced in the list of fields because it is an existing field. Presumably the data source of the form is a table or query and you need to edit the data source and remove the column that no longer exists.

 

[CJ_London]

It seems to be referenced at the add existing field tabs

don't know what you mean by this. You should not need to rebuild, just carefully inspect all the properties.

One other thing you can do is go to the documenter, select the form/forms and any relevant queries and click OK to see all the properties

 

[Tieval]

Presumably when modifying the form you can click on 'add existing fields' and it is present in the list of fields that can be added.

This is because it is set as a field of the form, this is why I suggest you look at the data source of the form as I assume it will be a query which has a field available in it that no longer exists.

 

[The_Doc_Man]

Just remember that a field reference not only occurs on a bound form's .RecordSource, but it can also occur in a query or in a combo/list box .RowSource, and can also appear in a form or report's .Filter (or is that .FilterBy ... I'm not where I can look that up at the moment). It can even happen in a relationship in a back-end even though the field name doesn't appear anywhere in the front-end. I would not have believed that last one if I hadn't seen it and torn out some hair because of it.