gigifarrow
asked on
How to I work around in query in SQL expression Exceeds 1,024 charactor limit in query grid design
I have a code that gives check marks values based on the production number. The code works fine. but when I go into to design view i get a message that the expression is exceeds 1,024 character limit. How do i change the code to comply with the character limit?
IIf([Production]>=168 OR [Production]<=128,
Abs(([tblFortCarsonFullup]
FROM tblFortCarsonFullup;
IIf([Production]>=168 OR [Production]<=128,
Abs(([tblFortCarsonFullup]
FROM tblFortCarsonFullup;
try removing "[tblFortCarsonFullup]!" from the query
or
go to the table [tblFortCarsonFullup] property and give an alias name F to the table
so your query will look like this
IIf([Production]>=168 OR [Production]<=128,
Abs((F![Induction]*5+F![De
FROM tblFortCarsonFullup As F;
or
go to the table [tblFortCarsonFullup] property and give an alias name F to the table
so your query will look like this
IIf([Production]>=168 OR [Production]<=128,
Abs((F![Induction]*5+F
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
<<Jdettman: I havent really dealed with functions before. Do I declare a function in the query in the sql design? could you please elaborate on how i would do this. >>
In Access, procedures are placed in code modules. Not sure which version your using, but you'd create a standard module and then do:
Public Function myCalculation(varInput as variant) as double
' Do calculations here
myCalculation =
End Function
and save the module. Then call it from the query.
You would need to pass in all the values from the query that you need for the calculation.
Often using a procedure can help keep logic clear when the calculation is complex and it's also good to use when you need data outside of what's in the query.
For this situation, cap's suggestion of shortening the table name is probably a good way to get around the error.
but if your going to add more to this calculation, then you may need to move it into a function even though your using a short alias.
Jim.
In Access, procedures are placed in code modules. Not sure which version your using, but you'd create a standard module and then do:
Public Function myCalculation(varInput as variant) as double
' Do calculations here
myCalculation =
End Function
and save the module. Then call it from the query.
You would need to pass in all the values from the query that you need for the calculation.
Often using a procedure can help keep logic clear when the calculation is complex and it's also good to use when you need data outside of what's in the query.
For this situation, cap's suggestion of shortening the table name is probably a good way to get around the error.
but if your going to add more to this calculation, then you may need to move it into a function even though your using a short alias.
Jim.
MyFunctioName(<somefieldna
You need to pass an argument even if it's not used so that the function is called for every row of the query.
Jim.