I have a similar situation as the previous post about crosstabs. Same type of error message, "Microsoft jet does not recognize [1] as a valid field name" etc. My particular query has worked in the past, but no longer...Not sure why. I have posted the problem field below in hopes that someone can tell me what's up. I was thinking of trying to automatically put in zero if there was no data for the field, just as a way to bypass the error message, but to be honest I'm still learning the access ropes and am not sure how to incorporate it into the current function. Any help would be greatly appreciated!
BTW, my database is a vacation/sick time rollover program and worked up until I set the new fiscal year date as 07/01/2004. I'm sure it has something to do with no one having used any time since that date. When I enter a fake employee who "used" a sick day on the 1st of July, then the error message changes to ...[2] as a vaild field name"
Thanks again!
Tara
The Value: First(Str([Sick-Personal Days]![Sick/Personal]) & Left([Sick-Personal Days]![type],1))
BTW, my database is a vacation/sick time rollover program and worked up until I set the new fiscal year date as 07/01/2004. I'm sure it has something to do with no one having used any time since that date. When I enter a fake employee who "used" a sick day on the 1st of July, then the error message changes to ...[2] as a vaild field name"
Thanks again!
Tara
The Value: First(Str([Sick-Personal Days]![Sick/Personal]) & Left([Sick-Personal Days]![type],1))
