Search results

Thanks Doc Man and Minty, my problem was picking a number from the table when I opened a form and rolling it on when I closed the form, if a user took their time all sorts of other things could go wrong when others interacted. I moved to a system of adding a record to the number table on entry...

I have a table of order items which is fully primary keyed, however I adopted a single order number field so I might have 100001 A007 100002 A007 100003 A007 100004 A008 100005 A009 Using the rolling last number table somebody might start to generate an order and when they have...

I have a database which has a table in the back end that stores the last used order number. When you generate a new purchase order it takes this number and adds one to generate an order number on a form. Once everything is done you close the form, save all data and roll the last used order...

In the open event you could use DoCmd.MoveSize to set the size and position of the form.

You may want to look at Minty's logics, I just looked directly at your question. I just changed the sub-form view to continuous form as attached and then messed with the layout a bit.

and change the main form order value textbox to =[Order Details].[Form]![Text13]

One thing to note here, although I hate datasheet views most people seem to love them. If you want a datasheet view you can always make a continuous form look like a datasheet view.

You cannot use a datasheet view for this, attached seems to work.

Unfortunately, having looked through this again, I may be wrong. Can you post the database so that I can take a look. I think you can just zip it and attach it.

Microsoft Partner Network costs £300 to join and allows ten installs of Office Pro 2016.

Access doesn't like doing two bits of maths. Instead of having a calculated field on the sub-form for total you need to put it in the query you used and display it as a value rather than a calculation. You will then be allowed to sum the fields.

Put in a query that the form is based on that the desciption is: Like "*" & [Forms]![SearchForm]![SearchTextbox] & "*"

It is a field that needs removing from your qry_searchlegatee - your subform is based on a query of that query, although the subform doesn't use it the base query still looks for it.

Thanks Plog, I have a touch of OCD and like to cram everything into one query where possible, I have the sub-query working but was hoping for a single stage solution. ;)

I have a simple query to throw up suppliers that have been used more than twice. Unfortunately my base data has: Supplier, Order Number, Item I want to group by supplier and count the unique order numbers as I may have three line items for order number 123 and two line items for 124 and want...

You have set the supplier as a look-up field in the table so it is displayed as the value of the number in the other table. You would be better just storing the number and relating it to the other table. When you then use your search form you can query the supplier name against the number. Tip...

I have added an example for clarity

The difference here is that I have a main form which is totally unrelated to the sub form, it is only a sub form for presentation purposes. The switchboard is a standard switchboard allowing control of all areas of the database (the usual thing). The difference is that I have two forms opening...

I have a continuous form with tick boxes in it, they can all be clicked to tick and untick. When I make this a subform within another form the tick boxes cannot be ticked or unticked. The sub-form is a completely unrelated form to the original form and is located in the footer of a switchboard...

You could convert it to a string and check if the length is greater than one. anymore offers:D