Update Query Issue

[Voodeux2014]

I have an update query in place that pulls the current device shown on my frmMainMenu and sets that as the current device. I want it to pull the information in a textbox on frmDevNameChange and have it change that devices name in the table so that the frmMainMenu will then display the new name. Problem is, it keeps saying that the textbox on frmDevNameChange isn't recognized. I can get it to work by putting the val option in front, but then it just sets a number. Any help would be appreciated.

[pbaldy]

Is that form open? It has to be. If it's a subform, the syntax changes:

Forms Refer to Form and Subform properties and controls

[Voodeux2014]

Yes, both forms (frmMainMenu and frmDeviceNameChange) are open. On frmDevNameChange I have the textbox there and have created an update query that I have linked to a button at the bottom so that it runs when that button is clicked. If I alter the query to Val([Forms]![frmDeviceNameChange]![txtNewDevName]) it will function without error, but has set the device name to a single digit number. If I set it to just the [Forms]![frmDeviceNameChange]![txtNewDevName] in the update to cell, it just gives me an error. Here is the exact error:

The Microsoft Access database engine does not recognize 'forms]![frmDeviceNameChange]![txtNewDevName' as a valid field name or expression.

[pbaldy]

Are the incomplete brackets a typo? What is the SQL of the query?

[Voodeux2014]

UpdateQuery.zipI copied the error exactly. When I go to double check the query it has the full brackets. I don't know what you mean what the SQL of the query is. I have taken a screen shot of the query design view as well as the error.

[pbaldy]

What I can see looks okay. Can you post the actual db here, or a sample that exhibits the error?

[Voodeux2014]

Here it is. Had to unsplit it and remove the encryption password haha.

[pbaldy]

Subtle change, but try

[Forms]![frmDeviceNameChange].[txtNewDeviceName]

[Voodeux2014]

Well all be, crazy how just one punctuation mark makes all the difference. Now is there a way to not have it pop up the are you sure you want to run this query pop up?

[pbaldy]

Wasn't coming up for me. You used SetWarnings in your macro, which would be the macro way around the warnings.