Search results

That's why I said one possible approach as I wasn't sure if your form was based on a table or not.

Try, unselect your current primary key. So your table does not have a primary key, you may have to destroy a relationship or two to do this. Then choose the primary key button and drag across your four fields in design view.

I don't quite understand what you mean by Autofill. However, in Excel the autofill occurs when you are repeating information previously entered. In Access we handle this slightly differently. Normally this information would be stored in a lookup table. This is a table that is related to the...

One possible solution could be to create a combined Primary key. This will work in Access XP I am not so sure about previous versions of Access.

The Form and Sub Form are Related by thier 'StockTakeID' numbers What I am trying to accomplish is to have the Sub Form display every stock item, when a new stock take is started These two statements are mutually exclusive. By relating the subform to the main form on the StockTakeID the...

You could consider trigerring a close of the subform from the main form, and in the subform test for a value on the main form. So something like: SubformCurrent IF Not mainform.chkClose then Do something End if In which case nothing will happen. Then toggle the value of chkClose in the...

Try force saving the record after you have grabbed its ID something like strID=Me.Company_Trust_ID Docmd.RunCommand accmdSaveRecord Now search for the record. No promises though I think I tried this a while ago, without much success.

Justify is not available, and i haven't found a work around yet.

I am currently playing with a second run at a design I have working in a prototype and trying to think outside the square. I have a subform which contains a combination of nested and synchronised subforms. As we move from record to record on the main form the subforms all refresh, and within...

I have a series of subforms which are synchronised, they all work great, as I scroll from record to record they change to the appropriate record. However, one of these forms is supposed to represent items on site. This form is set up to search by a combo box in the header of the form. This...

My last project was 127 forms. The approach I used on this was chopped the project up into seperate sections, for example client management, service management and so on. Worked on each as a seperate task group and then remarried the entire project back together and ran more testing to check...

I must admit I am not the tidiest person in the world. Having said that once I understand fully what I am doing I tend to design systems that become self tidying, but this can take years. Unfortunately this is biting me a little bit, so I thought I would ask how others organise. Specifically...

I think you also need an orders detail table. That aside. The principle of normalisation is to store information only once, and enter only once. That being the case if you want to display information about your book from your book table in the orders form then yes you do this by a query or...

One approach might be to add the last serial number as the default value of the new record. Another approach might be to have a subform, that displays the last three records or something like that. HTH

Have you considered using a sub form approach. The sub form would be a query based on the value in the combo box. In this way information would be queried to the specific project.

Change the criteria to 0 to return not null records.

Why not just open your other report invisibly then use this as the record criteria for your report?

I have had a few cases where this doesn't work in queries and don't know why. However, the workaround that works is to create a new field in the query. Expresion set as Iif(IsNull[MyField],1,0). Set the criteria for this field to be 1 and you will return all records where [MyField] is null. HTH

You may be able to make one query. Place all the tables in the design grid and link the UniqueID number. Drag the ID number from one of the tables and all the rest of the fields into the query how you want them. HTH

I think you are not saving the record in the first form. You may need to force save it for the second form to work correctly. docmd.runcommand accmdsaverecord hth