Address fields

[cfljanet]

We have recently upgraded to 2016 which is causing me a few issues. In one form I have an address field which references an underlying query in the following way: =[Consignee Address1] & Chr(13) & Chr(10) & [Consignee Address2] & Chr(13) & Chr(10) & [Consignee Address3], etc. The outcome is the address in a single field properly formatted.

This field has been fine for years but since we upgraded to 2016 it just returns the error #Name? However, in other forms which are syntaxed in exactly the same way (just referencing different address fields), they work fine. Putting in a single field name omitting the Chr syntaxes also work fine.

Any ideas? I have changed the field name which used to be "Address" just in case that confused it. It made no difference. I have checked the underlying query and the field names and data are fine. The field names appear in the Existing Fields of the form. So I can't see anything that could be upsetting it.



Would be grateful for any pointers.

[andy49]

Does chr$ make a difference?

[cfljanet]

just tried it....unfortunately not. I did search online to see if anyone else had the problem but couldn't really see anything similar except in reference to Access 2013 where the solution, apparently, was to upgrade

[andy49]

Are those values displayed anywhere else on the form

[aytee111]

What if you put that into VBA instead, does it work? I presume it is the control source, you could put it in the OnOpen event.

[cfljanet]

Not those same ones. On one side of the form I have Consignee details, so they are Consginee Address1, Consignee Address2, etc. and on the other side of the form I have Notify Party details so Notify Address1, Notify Address2, Notify Address3 etc.

[andy49]

Just wondered if you had a txt box the same name as the field?

[cfljanet]

Just wondered if you had a txt box the same name as the field?

No I don't. I did check that before posting. It seemed the most likely cause, although that would have upset it years ago, rather than just now (I think), as I haven't changed that form since the dinosaur era

[cfljanet]

You mean have an OnOpen event to populate that field? I could try. My VBA is rubbish, but I could try and work it out. What frustrates me most with these things is not knowing why it's happened, and I'm wondering what other little gems I will find

[aytee111]

Not populate the field, that would have to happen on each and every record. Set up the control source string. Have you tried doing it in the query itself?

[cfljanet]

Not populate the field, that would have to happen on each and every record. Set up the control source string. Have you tried doing it in the query itself?

YES, now I have! Built it in the query, I mean. It works! I should have thought of doing that before. Still don't know why it suddenly stopped working after 10 years or more, but at least it is working.

Thank you all for your help!