Search results

That's an interesting problem. The first thing that occurs to me is to split the data into two sub-reports, which run concurrently. Attached is an example of what that might look like.

I've been using this code for a database that is currently being used in New York, London and India. The New York and India users are having no problems, but the London users are now reporting that it still thinks they're on DST. It appears the StandardDate() function is returning November 4...

The problem now is that your Criteria and your result are the same thing: the InvoiceRef field. Do you really need to look up the Invoice Reference, or are you getting that value from the frmGenerateInvoice form? Just out of curiosity: is there a reason you want to return a random five digit...

Try putting the field names in brackets: xlook = DLookup("[InvoiceRef]", "tblInvoice", "[Criteria] = '" & Forms!frmGenerateInvoice!txtinvoicenotest & "'") I'm assuming that "Criteria" is in fact the name of a field in the tblInvoice table.

Thanks for the advice, Moniker. I have indeed gotten around this problem by using a SendObject instruction rather than the Hyperlink. The reason I prefer the Hyperlink, however, is because the SendObject demands that the user either send or close the email immediately. The Hyperlink allows the...

I'm trying this one again, as I still haven't found any acknowledgement of the issue. Does anyone know why a mailto: instruction that works in Access 2000 fails in 2003 if the character length goes somewhere above 450?

I've just come across a peculiar 2000 vs. 2003 problem. I have a form that generates an email via VBA code. The body text of this email varies depending upon the contents of the data tables. The technique I have been using is to establish a mailto: line, and treat it as a hyperlink. The code...

My first guess would be that your check boxes aren't bound to fields. Do you have fields for each of these check boxes in the data table to which this form is bound?

To find records where the static table differs from the linked table, you would set the field criteria to something like: <>[linkedtable].[addressfield]. If you also want to find records where new information exists, just change the field criteria to : Is Null or <>[linkedtable].[addressfield].

The "Unrecognized Database Format" error will frequently occur on workstations where more than one version of Access is installed. If a user attempts to open an Access 2000 file, but their profile associates MDB files with Access 97, you'll get that error. The solution would then be to...

Could you just change the Enabled property of the Criteria boxes? For the On Click event of each check box, use something like this: If Me.CheckBox1 = 0 Then Me.CriteriaField1 = Null Me.CriteriaField1.Enabled = False Else Me.CriteriaField1.Enabled = True End If

Is there a chance any of these fields will ever be null? If so, you might want to use Nz to account for such occasions.

Have you tried declaring NumOfComputer as an Integer instead of a Variant?

Select the field in question, and open the Properties box. On the Data tab, set the Locked property to "Yes". When the user enters the password, use an If Then statment to evaluate the result. If password = "CorrectPassword" Then Me.TextBox.Locked = False Else Me.TextBox.Locked = True...

You can use the "On Not In List" Event to run a macro or VBA code that will generate a custom message box.

I would recommend three tables. Your first table lists all of your contact information, and will be used to generate your form letters. The second table is a listing of all letters that have been sent out, and will only need to include two fields: the ID of the contact, and the date the letter...

Set the criteria to: LIKE "99*"

Don't bother with the find button. Instead, just put in a combo-box linked to your Truck Information table. Assign it two columns: serial number and truck ID. When the user starts typing the serial number, the combo box will autofill the rest of the entry. For your On Exit event on the combo...

Too true. In my firm, the act of downloading a password-cracking application is grounds for immediate dismissal.

There's a much easier way to do this. In your form frmCreateCAR, create a combo box populated by a Query linked to your Employees table (which I'll refer to as NameField). The combo box will contain five columns: 1) the employee ID number (or whatever your unique ID field is) 2) [LastName] &...