Recent content by TheWildHare

You could have also used "Between #" & [forms]![frmInvoice]![InvoiceRunFrom] & "# and #" [forms]![frmInvoice]![InvoiceRunUntil] & "#" Which would translate at runtime to: Between #10/1/06# and #10/31/06# Just another way to skin 'er....

Lushh - the automatic saving of a bound record on a form seems to be a 'feature' of Access that can not be disabled, per se. The way I've gotten around this when necessary (and it's ugly, to say the least) is to use a temporary table to hold the data on your 'working' form, and when the...

Dawn, you might be able to set a rectangle in the detail section, and in the section's ON PRINT event, reset the HEIGHT property of the rectangle to just a little bit less than the HEIGHT of the detail section. I'd test it here but my home copy of Access is a bit gnarled right now and it's 2 AM...

Martin, I agree with JimHorton, using Access Security IS the better way to go - and it's not all that difficult. I was going on your statement that you don't want users to log in, which they would do using workgroup security. I'd really suggest you check it out and seriously consider using it...

Your problem is one of grouping and paging, not of syntax. A Page footer isn't smart enough to know what's "above" it, physically. (A report footer is - EVERYTHING is above it...) Your best bet is to GROUP your details, and advance to a new page for each group, and then you can place...

Are you designing a FORM or a printed REPORT? It sounds almost like you are printing a FORM, which is considered "not good". If you have a REPORT designed with the appropriate page setup values, and make sure your printer is not reverting back to standard portait size, it should work...

Yes. Well, kind of.. almost...But I don't know what you mean by Maximizing a menu - ..to me, a menu is a one-line, rather horizontally oriented object of a fixed height. In which direction would you "maximize" a menu? There are a couple of guys that contain the current form's height...

Rather than wait until the user has skipped by all five (or seven or eighty-leven) comboix, why not check in the Lost_Focus of each combo: Sub CmbItem1_LostFocus if IsNull(Me!cmbItem1) then msgbox "Sorry, you must pick an option" Cancel = True End if end sub This cancels...

Yes. The ON CURRENT event is form (record) related, not FIELD related. I know of no way of programmatically altering the controltip text for a field. However, you might try this little trick. Place this code in your text field's ON GOT FOCUS event: Dim RegLength as integer RegLength =...

DoCmd.Maximize in the Report OPEN event.

1) Dim your second criteria as a DATE, not a string. 2) Concatenate the two - you can only apply one "filter" at a time, but it can be a compound filter StrCriteria = strCriteria1 & " and >" & "#" & Criteria2 & "#" substituting the appropriate logical...

Place the other reports as subreport object in you main report's Report FOOTER section. YOu can make them invisible so they don't show on the screen. OR... Place calls to the Docmd.OpenReport method, naming the other reports, in your main report's ON CLOSE or On Deactivate event. Either way...

Ski, don't put that DROPDOWN in the GotFocus of the combo, put it in the CLICK of the command button: Sub Cmd41_Click() With ME .Combo1.setfocus .combo1.Dropdown End with End Sub

1) disable the database window 2) control exiting/closings form by turning off borders (and hence the close/minimize/restore buttons) 3) make sure you exit access when you leave the main menu. 4) make sure you use a startup form and an autoexec macro 5) hide objects, so even if a user somehow...

check out my response to your later post..the DROPDOWN method..