By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,651 Members | 1,908 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,651 IT Pros & Developers. It's quick & easy.

#Name? Error... trying to link two fields in same form

P: n/a
I'm not sure if this is some random bug in the system, but I keep
getting the #Name? error on one of my forms when I try to link one
field to another. For example, I have one field called txtTrialField
which = date(). I then have a second field which =[txtTrialField]. For
reasons beyond me, it comes up with the above error. I'm actually
trying to make something a little more complicated but after an hour of
frustration, I reduced it down to this simple problem.

I swear it was working earlier in the day and the same arrangement
works on other forms. Does anyone have any idea why it would not work
on my current form??

Grrr :(

Cheers

Reg

Jan 3 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
What you are trying to do should work.

Try changing the Name of your text box. Access gets confused if it has the
same name as a field in the form's RecordSource, but it is bound to an
expression.

If that does not solve the problem, try unchecking the Name AutoCorrect
boxes under:
Tools | Options | General
Then compact the database.
Explanation of why:
http://allenbrowne.com/bug-03.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Regnab" <p.*******@gmail.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...
I'm not sure if this is some random bug in the system, but I keep
getting the #Name? error on one of my forms when I try to link one
field to another. For example, I have one field called txtTrialField
which = date(). I then have a second field which =[txtTrialField]. For
reasons beyond me, it comes up with the above error. I'm actually
trying to make something a little more complicated but after an hour of
frustration, I reduced it down to this simple problem.

I swear it was working earlier in the day and the same arrangement
works on other forms. Does anyone have any idea why it would not work
on my current form??

Grrr :(

Cheers

Reg

Jan 3 '06 #2

P: n/a
Thanks for your response Allen. Tried both things you suggested and it
still wouldn't work. It's hard to know for sure what the problem is -
I'm actually fixing up a database for a fella that didn't use naming
conventions etc so there could easily be some clashes that I'm not
aware of.

I ended up taking another copy of the original database and pasted my
text boxes with code into the same form in his other database and it
works fine. So while its certaintly not a pretty solution, it seems to
work.....

Thanks again - and I'll be happy to try other changes if you have any
other ideas because I would like to know what the glitch was.

Thanks again,

Reg

Jan 3 '06 #3

P: n/a
That's a fair enough solution.

Could have been a corruption. SaveAsText/LoadFromText could achieve the same
result, but your approach is as good as any.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Regnab" <p.*******@gmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...
Thanks for your response Allen. Tried both things you suggested and it
still wouldn't work. It's hard to know for sure what the problem is -
I'm actually fixing up a database for a fella that didn't use naming
conventions etc so there could easily be some clashes that I'm not
aware of.

I ended up taking another copy of the original database and pasted my
text boxes with code into the same form in his other database and it
works fine. So while its certaintly not a pretty solution, it seems to
work.....

Thanks again - and I'll be happy to try other changes if you have any
other ideas because I would like to know what the glitch was.

Thanks again,

Reg

Jan 3 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.