M
Marco Brilo
Hi,
I've run into a limitation in number of characters that can be used in the
Expression Builder the following expression:
[Forms]![MONITORING_DATA_ENTRY]![Abbr]
& "-" &
[Forms]![SEARCH_AREA]![SURVEY].[Form]![OBSERVATION].[Form]![Trap_Line_ID]
& "-" &
[Forms]![SEARCH_AREA]![SURVEY].[Form]![OBSERVATION].[Form]![Trap_ID]
& "-" &
[Forms]![SEARCH_AREA]![SURVEY].[Form]![Start_Date]
it gives me an error "Microsoft Access can't parse the expression:...."
but when I shorten the query by one expression i.e remove & "-" &
[Forms]![SEARCH_AREA]![SURVEY].[Form]![Start_Date] it works fine.
What I'm trying to do is get a field in the form to update when it gets
focus, the value has to come in from all over the forms and subforms I have
to create an ID.
Does anyone know if there is a limitation to how many characters are allowed
in the expression builder box? Is there a way to increase it? Any
suggestions how to fix this issue or work around it? I suppose one way would
be to use the ON GOT FOCUS to run a code instead of a macro but I was hoping
to avoid that.
Thanks in advance for lending your brain cells on this problem.
Marco
I've run into a limitation in number of characters that can be used in the
Expression Builder the following expression:
[Forms]![MONITORING_DATA_ENTRY]![Abbr]
& "-" &
[Forms]![SEARCH_AREA]![SURVEY].[Form]![OBSERVATION].[Form]![Trap_Line_ID]
& "-" &
[Forms]![SEARCH_AREA]![SURVEY].[Form]![OBSERVATION].[Form]![Trap_ID]
& "-" &
[Forms]![SEARCH_AREA]![SURVEY].[Form]![Start_Date]
it gives me an error "Microsoft Access can't parse the expression:...."
but when I shorten the query by one expression i.e remove & "-" &
[Forms]![SEARCH_AREA]![SURVEY].[Form]![Start_Date] it works fine.
What I'm trying to do is get a field in the form to update when it gets
focus, the value has to come in from all over the forms and subforms I have
to create an ID.
Does anyone know if there is a limitation to how many characters are allowed
in the expression builder box? Is there a way to increase it? Any
suggestions how to fix this issue or work around it? I suppose one way would
be to use the ON GOT FOCUS to run a code instead of a macro but I was hoping
to avoid that.
Thanks in advance for lending your brain cells on this problem.
Marco