Search results

In design view, right click on the "Detail" band and choose "build event". This is where you could "conditionally" format your report by VBA code. You could do whatever you want here including turning visibility off and on.

Try: If Me.Result = < 0 then Me.Checkbox -1 Else Me.Checkbox = 0 End If Substitute your own textbox names.

Try this code: If Me.Position = "President" and Me!Subform!Service = "B" then Me!Subform!Amount = 80 Else Me!Subform!Amount = 65 End If This is code (as written) need to be triggered from the main form, perhaps in the afterupdate event of a combo box where you select an employee...

You can try sorting your recordsource on the field "Serial" in your example. You have to choose either ascending or descending order. This will have the apperance of grouping certain fields that match. Not sure if that is what you want, but hope it helps.

You'll need another two fields in your 3rd table: - EmployeeID - EquipmentID making it 4 fields. Good luck on your project.

The requery should work. Where did you place the vb code to requery the combo box? This command should be issued on closing the form used to enter the new suburb.

It appears you are missing a "User ID" footer in your report design where you could calculate the result for each unique id using an unbound text box. In design view, right click anywhere on your report and add a UserId footer, then place your textbox and required calculation in it.

Do a little research on the following and you'll get your answer: - recordsetclone - bookmark - findfirst

In design view, right click anywhere on your report. This will open up a window that will allow you to do sorting and grouping without changing the underlying query.

You have to minimize the form where you are entering the required parameters. Do this before opening your report. This way, the form and its controls stays in memory and your report will not ask for the parameters the second time. On closing your report, issue another command opening your...

One approach you can take: - built a manufacturer table containing at least two fields namely

The syntax for insert statement is: INSERT INTO target [(field1[, field2[, ...]])] VALUES (value1[, value2[, ...]) with target being the destination table. Example: Docmd.RunSql "INSERT INTO tblInvoices ([CustID]) VALUES (forms!FormName!textboxname) ... where the value is coming from a form...

Try following the vba code in the on click or on double click event of your Add button. Somewhere there must be a command disabling a particular control that has the current focus. Try quoting it out that particular line to bypass it and observe if your program still does what you want it to...

Pat and Wayne's suggestions to use a bound form is the way to go. It is certainly easier. However, if you still want to continue using your unbound form, then my suggestion of running an SQL statements would certainly work. You can place the DoCmd.RunSql statements in the click or double click...

One approach you could use is to create a VBA code in the after update of each of the 4 text boxes on your form. You could use the following syntax: Docmd.RunSQL "UPDATE TableName SET TableField = Me.TextboxName WHERE CustomerID = " & Me.CustomerID Substitute your own table name, field names...

Using an update button is fine, but what values do you want in the four text boxes and where are the values coming from? Are you updating your tables based on the values you input in the 4 text boxes? You need to provide more details.

DLookup is the right function to use to get values from any table into a textbox. It has 3 parts: - the field you are interested in - the domain (table or query) - the condition (without the where clause) Which part are you having problem with?

You can use the On time event of the form to run a particular vba code every so often. The timer interval controls the frequency that the code is triggered. I believe 1000 is equivalent to one second, so if you put 5000, it should run every 5 seconds.

You may want to substitute the beginning date as the ending date where ending date is null. This might solve your problem.

It is my experience that running queries work faster than opening recordsets then adding new records via VBA (rs.addnew). Even running an sql statement via the DoCmd.RunSQL command works faster than adding records via recordsets.