Search results

To find a number: " [CustomerID] = " & Me.SearchBox.Column(n) The bookmark in your code will ever only find the Post Code - the preceding 5 FindFirsts will simply find the record but not bookmark it.

Cascading deletes won't solve your problem. The qry will still be RO as you are using an aggregate. Are you prepared to put a Delete cmd button on the form - I do this regularly and have it coloured 255 (Red). I then run VBA code to handle the deletion.

Andrew Why do you need 2 forms. Have one form with a cmd btn on it with the following code: DoCmd.GoToRecord , , acNewRec The above puts up a blank entry for a new record. You can also put a cbo on the form to find existing records. I can post a routine for this if you so desire.

Easy way to see: 1. If the cmd btn works 2. How the code executes How to do it: Open the code associated with the button and click in LHS "scroll bar" next to the "If Me.Dirty ...". A big brown dot appears and the "Me.Dirty ..." will also be brown. Save and return to the cmd btn and click on...

Whilst the above is correct, I think you can see the pwd as it is typed in. If you use a form and select the Input Mask as Password (one of the options), it replaces the characters you type with * or something similar. Private Sub txtPassword_AfterUpdate() Dim stDocName As String...

There seems to be a lot of questions on dates using the UK format. I use the following to maintain consistent results. Whilst the American format for dates is Month/Day/Year there are a lot of countries, eg Great Britain, that use the format of Day/Month/Year. This brings up some...

A very good explanation.

Brian Best way is to use the Format fn: eg = Format(varDateBooking, "dd-mmm-yyyy") Notice the 3 m's - this will force any date to UK date format - but if you use 2m's it doesn't seem to.

The ways that come immediately to mind are: Run an updateable qry as the Recordsource for the subfrm - probably not possible. If you can identify the record(s) that need deleting, run VBA code to do it. Can you trap the Delete key with an "OnKey" event?

By the looks of yr qry, it would not be updateable and therefore is RO. Run the qry on its own and look at the bottom of the recordset - if the * is grayed out then it is not updateable, hence RO.

I was referring to the 1st sentence.

Missingling What you have said is not strictly correct. I have seen a normalized tbl with nearly 200 flds. Most of these are flds that contain data that needs to be reported every 3 mths to a govt authority (flds are dynamic) so don't need a sub tbl.

Bill I've had a quick look @ yr tbls and it seems that there are a no of issues there to do with fld names and db normalisation (eg repeating flds in a tbl). Here are my suggestions: 1. In general, get rid of all spaces in fld names eg use xxxID instead of xxx ID. VBA doesn't like spaces...

I'll need to think about that. Can you post a zip file of the db with some dummy records in it?

Set up a continuous form and use the Format -> Text Align for each of the Controls.

If the 2 subforms are running an autonumber and you try and link to the main form then that's why it won't work. Can you have the ClientNumber in the 2 qyrs running the subforms - I assume ClientNumber is a PK in the Client Details tbl. The Parent Child link will then be the ClientNumber.

Try this: On the subform have a text box "Height" (Me.Parent!ControlName) where ControlName is the name of the "Height" text box on the main form.

Brian What are the Parent Child link flds between the main form and the 2 subforms.

Bill You have 2 problems here: 1. Many to many - you have to create another table with 2 flds (the join flds in the 2 many to many tbls). Then re-create the qry with this tbl added. This will get rid of the duplicates. 2. For a qry to be updateable, you can only have one join fld set to...

I put mmm/dd/yyyy in the Format ppty of the table and it showed Apr/14/2009. I set up a tbl with DateStart as the only fld, put in a couple of entries and ran the following qry. SELECT tblDates.DateStart, #6/1/2009#-[tbldates].[datestart] AS DD FROM tblDates; It definitely worked with the...