Search results

No I haven't been here long, the difference between me and you is that I won't put up with his crap. I won't get in feeble arguments with someone who obviously doesn't know what he is talking about and merely makes generalizations according to what stereotypes he's heard about. I have said...

Both copied directly from your posts.

One more thing Ken, Reporting people? I don't know why anyone would unless there was something very personal and/or offensive. I have come across neither of these in anything that I have read.

When not too long before you were taking it as an insult. You start arguments and then back down, what kind of redneck are you? I'm proud to be a beer drinking, dirt track racing, down home redneck. I would never take it as an insult. When somebody tries to use it as one, it does nothing more...

Col, it seems to me, through reading most of this garbage that you and Ken have been bickering about, that you are the epitome of every brit I have ever met in my entire life. Granted I haven't met many, but all the ones that I have look down their noses with that arrogant, pompous attitude. You...

Lets hope not

Two Brits are walking through the woods when they come across some tracks. The first says to the second, "I say, I believe these are racoon tracks." The second disputes the first saying, "No old boy, these are most obviously deer tracks." The two begin to argue for some time when finally, they...

the between...and statement should be inclusive (including the start date and end date). I use this in my databases and it includes the end date in the range. I'm guessing that you initially tried between forms![formname]![cbostartdate] and forms![formname]![cboenddate] This is what I use for...

You are probably right about the [;] versus [,]. Also make sure that [columnname] isn't the same as the text box name that you are defining. If this is the case it usually gives you an error about a circular reference.

Don't need two iif statements Your syntax isn't quite right. It should look more like this =iif([columnname]<1,"<1",">1") Essentially what this says, is that if [columnname]<1 then put <1 in the text box and if it is not <1 then put >1 in the text box. I may not be understanding exactly what...

A little more clear Build the macro with a condition that states the criteria you need to check. example: Condition Action Argument forms!formname.formvalue<1 OpenForm formname1 forms!formname.formvalue>1...

Build the macro with a condition that states the criteria you need to check. example: Condition Action forms!formname.formvalue<1 OpenForm forms!formname.formvalue>1 OpenForm Then set the OnClick event to run this macro.

I agree with Garry, I think this particular warning is being generated by Windows itself and not Access. If this is the case then SetWarnings will not stop this warning from happening. boblarson has a good example of how to stop this warning.

You don't have to use VB. Open the properties for the text box in your report and put the iif statement in the control source field under the All tab.

glad it worked for you.

Criteria statement Put this in the criteria in place of the between...and... statement (Between [Forms]![formname]![startdate] And [Forms]![formname]![endate]) Or ([Forms]![formname]![startdate] Is Null And [Forms]![formname]![endate] Is Null) If you leave the fields blank then it will return...

This is true. But he wants to delete everything older than that date, hence the date <

boblarson is correct. I typically use a form for things like that unless I just need a quick and dirty solution.

Hope this helps Hope this helps

Without having the start and end dates as actual fields in your query, you can't. What you can do is make two new fields, Expr1:[Enter Beginning Date] and Expr2:[Enter Ending Date] in your query. Then in your report make Expr1/Expr2 the control source. When you make the report it will run the...