Recent content by plog

SELECT Contact_People.* FROM Contact_People WHERE (((Contact_People.Category)<>"Accounts")); This should work as long as there is data in Contact_People.Category. It will not include NULL values of Contact_People.Category. You must specifically address NULL values.

It can be, but not in this instance. You've got multiple [Family] and [Genus] fields in the underlying datasources so the SQL will throw an ambigous field error without the table prefix. Of course, that would be an error you'd get once you fix this syntax one. I suggest an alias for the...

I'm looking closer now. Have you given us the full SQL? Usually in an unmatched query there is a WHERE dealing with NULL values in the LEFT JOIN source. Also... ...Bad_Family.Family" Is there another JOIN? Where is Bad_Family? It isn't in the FROM nor JOIN you have given us.

There is no missing operator, its the spaces in the table name. It either needs to be bracketed in the second instance, or assigned an alias in the FROM and the alias used in the JOIN.

Why did you bracket the first instance of sTable but not the second?

This is complicatedly simple. I think a lot of experienced people would miss it. The only reason I see it is my new reading glasses. You've got 4 double quotes in that expression. The third one looks funky (look very closely at your last post, they look italicized almost), i don't think its...

And what was the actual code you put on the Report? You didn't just paste what cheeky typed did you? You changed it to the actual name of the field in your database, right? Lastly, the name of that control on your report, it should be different than the field name you use in the table--since...

My guess is you were incorrect and do not have a Yes/No field. Go into the design view of the table and tell me exactly what the data type of the underlying field is.

It's like your mind is stuck on doing this with a DCount and you can't actually see what you truly want. The number of records is irrelevant, you really just want the sum of the Qty field of all records meeting your criteria. I defy you to provide an example that can counter that last...

That's neither "every" (it's just one) nor "is" (it's not a situation in the present tense, its future imperfect) a reason to store this data. If in the future the commission does become variable or changes at all, the cost/pain of switching over to a table system that does store it is very...

There's no reason for the commission to be stored. You build a query, use math in that query to calculate the commission then reference that query when you need the commission.

1. How is the commission determined? Flat rate->e.g. $10 per purchase regardless of size? Percentage->%5 of purchase? Other? 2. At what level is the commission set? Is it universal no matter agent/buyer? Is it tied to the agent? Is it tied to the buyer? Can every agent/buyer...

The google API is like the continuum transfunctioner, it's mystery is only surpassed by its power. I'm pretty sure you can do this, but it's going to take some digging. Start here: https://developers.google.com/maps/get-started/ Wrestling with setting up your Google credentials is the first...

Perfect. You need to change your ExpDate field to catch those 0 values: ExpDate: iif(Expiration<>0, DateAdd("m",[Expiration],[DateCompleted])) ExpDate will populate for non-zero values of Expiration and remain blank for 0 values.

Semantics time---do you want to not show any of the dates? Or any of the records? There's a difference: FirstName, LastName, DateCompleted, Expiration, ExpDate John, Smith, 4/24/2024, 0, 4/24/2024 Bob, Jones, 4/1/2024, 10, 4/11/2024 Sally, Metz, 4/2/2024, 2, 4/4/2024 Suppose the above data...