Search results for query: *

You should not store the calculated value in the table. Not only does this violate the Normal Forms, it's completely unnecessary. You may display the Expiration Date anytime you wish (without using a query, although I would recommend using a query. Why do you have a problem with that?). In an...

Yes, use a query for the source of your merge data. This can work from either the Access side or the Word side. From the Word side you would use the Merge Document Wizard, select the DB and query for your source. From the Access side there are several ways to do this. My favorite is to create a...

Actually, you shouldn't store a calculated value in your table. No attribute should be dependent on any other (non-key) attribute. You should, in fact, simply include the field as a calculated one in the form or report's underlying recordset. As soon as the field the calculation is based on is...

You're welcome. "Advice is a dangerous gift, even from the wise to the wise, for all course may run ill." J.R.R. Tolkien

GKProgrammer: Just an FYI. You can use the following syntax instead of what you are currently using: Me.[830to9].Enabled = Not Me.[830to9] rather than the longer IF statement. "Advice is a dangerous gift, even from the wise to the wise, for all course may run ill." J.R.R. Tolkien

Make sure that no other controls have the tab stop property enabled. Then, make sure that the last thing the button that sends the data where you want it to go, sets the focus back to the barcode input field. Any other buttons (i.e. close, or whatever) should also have as the last thing they do...

This syntax should also work for you: Forms!MainFormName!SubFormName!ControlName "Advice is a dangerous gift, even from the wise to the wise, for all course may run ill." J.R.R. Tolkien

Sounds like a problem with the references on some of your machines. Short of changing your recordsets to late binding (not recommended due to potential issues with performance), you can check the references on the offending machines to see if any are missing. If none are missing, you can usually...

Any property can be set using the following syntax: ObjectName.Property = {Expression} Simply insure that you use the full path to the Object. For example, if the property is a Form property and the form is open you can use Me. Or you can use the name of the form, FormName.PropertyName...

What do you mean by "no way"? "Advice is a dangerous gift, even from the wise to the wise, for all course may run ill." J.R.R. Tolkien

Try adding a prompt to the []'s Like [Enter Number] "Advice is a dangerous gift, even from the wise to the wise, for all course may run ill." J.R.R. Tolkien

Do not store calculated results in your table. Not only is this unnecessary, it can potentially be innaccurate. Instead, use a query to calculate the totals on demand. Base a query on the employee table. Add the status field to the QBE grid twice (put two copies on the grid). Press the sum...

You'll need to send the fieldname with each criteria. Use the following syntax: Private Sub List0_AfterUpdate() Dim varItem As Variant Dim txtTemp As String Dim txtCriteria As String txtCriteria = "[CriteriaFieldName] = " txtTemp = txtCriteria For Each varItem In...

My suggestion will not work as the criteria for a query but will work to build the SQL of a query directly or to pass as the WHERE claus when calling a report. To use as the where claus when calling a report you set the field to the criteria: DoCmd.OpenReport "ReportName", ...

You're welcome. "Advice is a dangerous gift, even from the wise to the wise, for all course may run ill." J.R.R. Tolkien

You must set the criteria in the report's underlying query to the form's date fields. This hasn't changed. "Advice is a dangerous gift, even from the wise to the wise, for all course may run ill." J.R.R. Tolkien

If you plan on using the same form for multiple reports you'll need to pass the report name to the form so that it will let your user put in the dates then open the correct report. A better method would be to open the form first, let the user fill in the dates, then select the report to run from...

To get them on the report use their full path in an unbound control on the form just as you did in the criteria of the query. =Forms!FormName!DateFieldName put this in an unbound control's controlsource property (make sure you substitute the actual formname and control names for the...

It isn't a statement. It is a property of the report. There is an icon on the toolbar for grouping/sorting. Press this button and you'll get the grouping/sorting dialog box. You can set your group level here along with whether or not you want and header or footer for it. "Advice is a...

You're welcome. "Advice is a dangerous gift, even from the wise to the wise, for all course may run ill." J.R.R. Tolkien