If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
#NAME? problem
I have 2 tables with a relationship and enforced referential integrity
selected. When I use the Query in QBE or in a Form or Report it is hit and miss. Sometimes it works, and sometimes I get #NAME? in the form's fields, and when it is not working on a report I get a prompt for the fields. Each table has an autonumber key, one table calles it key and the other record. The tables are staff info and the other staff training, so I match on FileNumber. An ideas..... |
#2
|
|||
|
|||
You don't give us much info, but my first guess is that one of the following
(or more than one of the following) is occurring: (1) You're using a reserved word as the name of a field or control, and ACCESS is confused by what you mean. See this Knowledge Base article for more information: ACC2002: Reserved Words in Microsoft Access http://support.microsoft.com/default...b;en-us;286335 (2) You have a control on the form or report that is named the same as a field in the query, but that control is not bound to that field. Again, this can confuse ACCESS over which you meant to use. You'll need to give us the SQL statement of the query, identify the structure of the tables and form and report, and if possible identify some examples of which combinations have given the error that you see. -- Ken Snell MS ACCESS MVP "Lisa" Lisa @discussions.microsoft.com wrote in message ... I have 2 tables with a relationship and enforced referential integrity selected. When I use the Query in QBE or in a Form or Report it is hit and miss. Sometimes it works, and sometimes I get #NAME? in the form's fields, and when it is not working on a report I get a prompt for the fields. Each table has an autonumber key, one table calles it key and the other record. The tables are staff info and the other staff training, so I match on FileNumber. An ideas..... |
#3
|
|||
|
|||
I do have a reserved word as a field name - I assumed Access would not let me
do that... Thanks, Lisa "Ken Snell [MVP]" wrote: You don't give us much info, but my first guess is that one of the following (or more than one of the following) is occurring: (1) You're using a reserved word as the name of a field or control, and ACCESS is confused by what you mean. See this Knowledge Base article for more information: ACC2002: Reserved Words in Microsoft Access http://support.microsoft.com/default...b;en-us;286335 (2) You have a control on the form or report that is named the same as a field in the query, but that control is not bound to that field. Again, this can confuse ACCESS over which you meant to use. You'll need to give us the SQL statement of the query, identify the structure of the tables and form and report, and if possible identify some examples of which combinations have given the error that you see. -- Ken Snell MS ACCESS MVP "Lisa" Lisa @discussions.microsoft.com wrote in message ... I have 2 tables with a relationship and enforced referential integrity selected. When I use the Query in QBE or in a Form or Report it is hit and miss. Sometimes it works, and sometimes I get #NAME? in the form's fields, and when it is not working on a report I get a prompt for the fields. Each table has an autonumber key, one table calles it key and the other record. The tables are staff info and the other staff training, so I match on FileNumber. An ideas..... |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Big Problem. We need the fix | Captain K | Calendar | 0 | July 8th, 2004 04:50 PM |
Passport Logout Problem | Chen qiang | New Users | 0 | May 4th, 2004 09:26 AM |
Help Microsoft? WORD11.ADM File Problem Line 818? | Dwight Hutchinson | New Users | 2 | May 3rd, 2004 08:25 PM |
Word 2000 footnote problem: footnotes consistently too high (again) | Lori | Formatting Long Documents | 2 | May 1st, 2004 07:15 PM |