Search results

While the VB Case convertors work OK, they don't handle some names correctly. I wrote/butchered the following code some time ago when preparing a mailing list for a company. Paste the code below into a new module and use the Mixed_Case routine. Public Function Mixed_Case(str As Variant) As...

Simon, The advantage of like is that with queries it will find all instances of "NORMAL" for instance( NORMAL, NORMAL2, NORMAL3) so that you can with one section of your code turn off all the "NORMAL" controls, but then turn on "NORMAL2" later by using = "NORMAL2". Thats how I use it...

enter Date() in the default value property of the combo box!

In the underlying query for the report set a criteria for a unique field (say account number). the criteria should be; [FORMS]![NAMEOFFORM]![NAMEOFCONTROLONFORM] When the report prints out, it will only get the record that is screen, because that record will be defining the criteria.

The answer from simongallop will work fine, but below is a solution I use to setting the visible property for controls on forms. All you have to do is put a value in the TAG property of the control (say NORMAL for demo purposes) for every control that you want to hide or unhide and use the code...

Using "is null" can be a bit of a fallacy. I have performed similar operations on forms and would recommend that you try; = "" instead of "is null". Checking the contents to see if they conform to a state of null ness doesn’t work because there is nothing there.

I always find domain aggregate functions to be troublesome (although at times they are just to useful) Your dlookup should be like this; =DLookup("[Quantity]", "ComputerPartsDetail", "[PartID] = _ & [Forms]![SysBuildInvCat1Ver3]![Text2]") Hope it works.