Recent content by cheekybuddha

One thing to double-check: With table [Date calc] in design view, what datatypes are DueDate and DatePaid ? Or if [Date calc] is a query, what is the SQL of the query?

Follow my instructions in Post #17. If you don't know how to do it, then let us know.

Switch you query to SQL view. Copy and paste the SQL here. We can show you the corrected SQL. Then you can paste it over the SQL of your query. Then switch back to query view and you will see how it is constructed by Access in the query designer.

With [Expr1], you are comparing with a string instead of a number. Try: Expr1: IIf([Days]>4,"Yes","0")

See my post above - please post [Expr1]

We need to know how [Expr1] is calculated (ie what is the expression). Since you are coercing to a boolean, if [Expr1] returns any value other than 0, then it will coerce to True ("Yes"), even negative values. In Access/VBA the value of True is already negative (-1).

You missed the point of 'the three generations of a family'. That is purely to describe the relationship between the tables employees, enrolments and cafeterias. There are no actual grandfathers, fathers or sons. It is a [mis-]translation of parent table / child table / child of child table.

Please share your final solution. It will help other users here who may have the same problem.

It would help if I could read properly! 😬 Glad you worked it out! (y)

Hi, Just test before adding the report name if required: ' ... For Each obj In CurrentProject.AllReports If Left(obj.Name, 3) <> "sub" Then NewValList = NewValList + Chr(34) + obj.Name + Chr(34) + ";" End If Next obj ' ...

Really you probably ought to fix the design of table daso455 and whatever is tableb Having seven fields named c1 ... c7 is a really poor design (search 'normalisation') that will require you to perform these kinds of code gymnastics. With a better table structure the result could probably be...

Try: SysCmd acSysCmdRemoveMeter at the end of your code

Here is a link to some code that you can run, so that classes in your library can be instantiated using the 'New' keyword in you application code.

Yes, but where did it originate in this thread? Where does the screenshot in Post #9 come from?

Make the ControlSource of the textbox something like: =IIf([YourYesNoFieldName] = True, "Yes", "")