Search results for query: *

dhookom I see what you mean now. I'll read it again! Thanks, Terry

Hi dhookom Yeh, I found that article and read it early on but it wasn't quite what I wanted. It wasn't so much a question of printing the totals in same place on every page. I didn't have any problems with that, using the page footer, but more a question of not printing them at all except on...

Hi JoeAtWork Thanks for responding. I'll have a play about with your suggestion. It's difficult to shorten the part with the invoice totals on because I want the invoice to look pretty conventional, showing Net, VAT and Gross totals, along with payment terms and all that. Anyway I'll have a...

The above works well for a report designed to print several invoices at once, where any of the invoices could have more than one page. Another solution for a general report, where you only want totals on the last page, is to compare the controls: [Page] and [Pages] to determine when you're on...

I've worked it out now. I compared the item line count, in the detail section, with a running sum of items printed so far, in the group footer section, to determine if the totals should be visible or not. They're only visible on the last page, when the running sum equals the count. Terry

Hi all Point me in the right direction? I have a multi-page invoice report. The totals are populated by the On Format event of the page footer. I want to omit (or make invisible) the totals on all pages except the last one. I don't want to use the Report Footer section since it seems to...

Hi TheAceMan1 Yep, that did. Many Thanks. I should have worked that one out for myself, I guess. Thanks again Terry

PHV Sorry, got your name wrong - its been a long day. Terry

Hi PVS The combo box would only visible again once the form has been closed and reloaded from a switchboard. The idea is that the user mustn't be allowed to change to another record until the routine (which is complicated and has to do with allocating payments in accounts) is satisfactorily...

Hi All I know it's easy enough to make a combox invisible, but what I want it to be invisible (o disabled) as soon as I've used it to select and display a record. I tried this in the After Update event of the combo box: Me!Combo92.Visible = False but it didn't work. Any ideas: So the...

Hi TheAceMan1 Yeh, that did it. Cheers mate. Terry

Hi all I have an Orders Form and an Order Items sub form. I have "Add" command buttons in both so that the user can add a new order, or add a new item to an existing order. On the sub form I can obviously put code in the On Click event of the button to set the focus to a particular field, to...

Hi TheAceMan1 Yes, the subform is linked to the mainform with Link Master/Child properties. I think I've worked it out now. The subform could create records just by using the record selector at the bottom, and going past the last record, so it was easy for the user to inadvertently create new...

Remou The fields are being populated by user input. You see, what happens is that the user wishes to set up an order record, typing in things like Order Date, Customer Code, (Order no is self-incrementing) and may wish to save the order, coming back to later to type in what could be several...

Hi Remou That's doesn't seem to be working as I want. It does stop a blank record from being saved but fields derived from a stock code combo box are now not working, so the record won't populate. Any other ideas? What's the reson for the "cancel = true" part? Terry

Hi What's the best approach to deal with this? I have a orders form, with an order-items subform, in a one to many relationship. The user clicks a command button to add an new order, fills in some fields and then, may or may not add order items at that stage. The order is automatically saved...

jk10 just read another similar post and dhookom (Programmer)had the answer as follows: "Don't close the form if you need values from it in the report. Just set its visible property to false." This worked, so thanks to him, and thanks again to your good self. Terry

Hi jk10 Same result I'm afraid. I'll just have a to have two command buttons - one for preview and one for print. Not ideal! What's more interesting is that it only works on the first page if it's a multi-page report. Wish I knew what was going on. If anyone's got a better way of doing...

jk10 OK, I'll give that a try when I get home, and let you know later. Many thanks Terry

Hi jkl0 Thanks for your reply. Your code works just like mine, in preview, but not in print. But just to clarify: If I use this: DoCmd.OpenReport ReportName:=strRptName, View:=acPreview, WhereCondition:=strWhere It works in the preview on the screen but doesn't if I go straight on to print...