Search results for query: *

Go to your Start menu, and select "Run". Type "regedit" in the Open box to open the Windows Registry Editor. Select HKEY_Current_User, and hit Ctrl+F to start a Find. Search for any entries with your name as the Data. (F3 cycles to the next entry). When you find a record...

I don't know if this will help, but I have databases that get the "too complex" error if records are missing certain data. If, for example, it needs to evaluate the distance between StartTime and EndTime, but EndTime is null for one record, the query will fail. Try setting criteria on...

What about a Windows registry key? Is there anywhere in your Current User profile that your full name is stored? If so, you can write a module that will call the contents of the registry key.

Is it possible that your records contain a single date and time stamp? (i.e., 10/14/03 17:30:00) If so, this time is not between 17:00 and 18:00, because short times would refer to Jan. 1 of 1900. If this is the case, then you need to add your Date and Time fields together, then check to see if...

I assume you mean each record has a single value in this textbox, and that you want to sum the field entries for the entire table. In that case, a DSum function would probably be the easiest choice.

Just curious; does the form HAVE to be bound to the query? Could the form be unbound, with the query results displayed in a table?

Set the form's AfterUpdate event to: Me![FieldName] = Now() & Environ("UserName")

Are you checking to see if the value of the box is 0 or -1?

Set the form's On Open event to: DoCmd.GoToRecord,,acNewRec

I personally would attach it to a Command Button that would also contain the code for generating your New Record. I do see one potential problem with what you're doing. Your user fills out the form, then hits New Record, and all of the fields remain exactly the same. How does your user know...

I do multiple criteria searches without any VBA all the time, just by setting up the proper query. Suppose you have a form with two fields: CityLookup and CompanyLookup. You want to be able to look up all customers in a particular city, all customers in a particular company, or only those...

It may not be the list box that's causing the problems. Are you certain that your query produces an updatable recordset?

Incidentally, when the entry form is complex enough, I find it helpful to use two separate forms: one for new entries only, and another for viewing existing entries.

Use the DoCmds. You'll live longer...

Sure, just make a report containing text fields which refer back to the form (i.e., "=Forms!MyForm!Field1"). Then, on the On Click event for the button, use this code: DoCmd.OutputTo "ReportName", stDocName That should do it.

What I always do is set up your combo box with the index field (usually called "ID") as the first column, and call it "LookupBox". Then all you need to do is set an On Exit event for Lookup Box: DoCmd.GoToControl Me.ID.Name DoCmd.FindRecord Me.LookupBox That should be all...

The formatting of the dates should be irrelevant. The only question is: WHERE do you want to sort it? In a query? On a report? On a form?

Alternatively, in the On Exit event of combo1: Me.text1 = Me.combo1.Column(1)

It's possible the DLookup is waiting for a Refresh event. You could try putting an On Exit Refresh event on the SSN field. If it were me, however, I would scrap the whole DLookup formula. Instead, I'd make the SSN field a combo box with two columns: SSN and Name. The Name column would have a...

Sure, just set an On Exit event for the Comments field that reads something like: If Me.OrderStatus = "Completed" and Me.Comments is null Then MsgBox "Yo chump! You didn't fill out the Comments field!" DoCmd.GoToControl Me.Completed.Name End If