Pat Hartman said:Sorry, that function is probably not available in earlier versions. Replace WeekdayName(Format([ClassDate],"w")) AS ClassWeekDay with Format(whateverdate,"dddd") AS ClassWeekDay
WayneRyan said:Ms,
That's a References problem. Use the search facility here. It is quite
common.
Wayne
smercer said:I already tried to run the query and I got an error as I said before. I got a different error when I ran the report as I said before.
See attachments
MsLady said:oh smercer i think i know why!
I linked it a textbox to a vb calendar i downloaded, so that when the user clicks on the textbox, a calendar popsup where they can choose the date from.
If you go to the form labelled "form1".
There's a textbox for DateReserved.. click on the "Event procedure" to that take off the calendar function.
I'll find a better way to do that so that my application won't go crashing people's computer..LOL hey im still learning.
![]()
smercer said:I did what you said and now I get a different error for the query. see attachment
I am still geting the same error for the report
Now as I said before about the format function being in a query, I think it is making things worse. if you want the results to display differently in the form or report you can always use the format function there. (at least try it)
smercer said:I can gain access to some reports via the button in the form. but not the report that you want to work.
here are a few tips:
1) when you are making a query and want it to ask the user something, you have the question in two squire brackets "[]" (see attachment for a tutoral on making a parameter query). this is an excellent tutoral because it shows you how to make the query based on what you have in the form on that record.![]()
2) your parameter querys are hard to understand. you want it user friendly and ask the user a question they will understand (in english, not in computer language). I dont mean to be rude but it is very hard to understand.
3) your form design looks good. it is very easy on the eyes and does not cause eye strain (a good thing if you look at it all day)
3) your form design looks good. it is very easy on the eyes and does not cause eye strain (a good thing if you look at it all day)
this may be because you may be behind the times and have an older version of office (or very new). I am using Office XP.MsLady said:smercer, guess what! i just tried it at work now!
It doesnt give me that format error. .. hmnn.. very strange. Everything opens perfectly.![]()
I have never used crosstab before so I can not help much.MsLady said:Im using crosstab now.. do you know why this gives me #errors?
Pat Hartman said:I made a calendar type report recently. It may be more complicated than you need because it has to use crosstabs and even a function to get some data. But the report has pretty colors and the queries may help you.