Search results

  1. D

    Solved Referencing a field within a RecordSet...

    You didn't provide a suggestion to "the problem" - you provided a suggestion to solve a problem you thought existed. I added my "Note" to avoid people immediately jumping in with the holier than thou data architecture arguments about 1-many relationships and how "keeping data in both places is...
  2. D

    Solved Referencing a field within a RecordSet...

    I just removed "me" ... the explanation mark stays "![LotN_QtyPlanned] Yes, the other "x" items are user-entered controls and variables from the form ...
  3. D

    Solved Referencing a field within a RecordSet...

    Pat: this response just isn't helpful at all - it doesn't provide a solution nor does it even address the problem of my post. Alas, I even tried to suppress your temptation to bloviate by including my "Note" at the end of the original post.
  4. D

    Solved Referencing a field within a RecordSet...

    Doc Man, THANK YOU! That didn't work, but I removed the "me" and it did the trick. Effectively, just matching the format of the other recordset fields. ![LotN_QtyStart] = Me![LotN_QtyPlanned]
  5. D

    Solved Referencing a field within a RecordSet...

    Hi - could use some help on what is hopefully a straightforward nomenclature issue... I have a button on form that when clicked, updates the form's data (4 fields from Tbl_BatchRecord) into multiple transactional records (Table: Tbl_LotN) via a record set. All works great to transfer this data...
  6. D

    Solved Creating transaction records via OnClick - (Sales Order to Invoice conversion)

    .... Added the CurrentDb, and then enclosed the two fields with a set of " ' " so the SQL statement read correctly. Put a save in to create the header detail record so that the children could be populated, and it now works great. Thanks for the help! Dim NextInvID as String Dim...
  7. D

    Solved Creating transaction records via OnClick - (Sales Order to Invoice conversion)

    Hi Paul, so I tried a modification of the above code, but throw a run-time error '424' Object Required on the db.Execute strSql, dbFailonError. Dim NextInvID as String Dim strSql As String NextInvID = 'code not shown but it generates a value 24V-##### strSql = "INSERT INTO...
  8. D

    Solved Creating transaction records via OnClick - (Sales Order to Invoice conversion)

    I've confirmed the data part is working - I built the tables, pre-populated invoice detail data and it shows up, as required in the forms. The 'data part of this' was described in my original post listing the tables, fields, primary/foreign keys. But to clarify in words: > SalesOrder Header...
  9. D

    Solved Creating transaction records via OnClick - (Sales Order to Invoice conversion)

    An invoice is a record of a shipment, not just an order. I'm not saving the same data twice because the data can be different. Example: Customer A orders 5 units of Product X. On Day 1, we ship and invoice 2 units at price A+5% for same day-turn around. On Day 18, we ship and invoice 2...
  10. D

    Solved Creating transaction records via OnClick - (Sales Order to Invoice conversion)

    I am updating a legacy Product Management Database to include Sales Order and Invoicing functionality. I am struggling on how best to create the invoice detail records (converting SO detail records to INVC detail records) and could use some advice on approach and/or specific code to include in...
  11. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    Errors out in the old report, works like a charm in a direct copy of the report with a "2" appended to the name. And yes, I'm in the process of removing my report name spaces :)
  12. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    SOLUTION: Create a form with two buttons and assign the "On Click" code as follows. This drives the OpenArgs to the report (which is only available on an 'on open' event. Private Sub PrintButton_RptSObyProductLevel0_Click() DoCmd.OpenReport "Rpt - SO by Product2", acViewPreview, , , ...
  13. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    Ayyy, something somewhere must have been corrupted!!! I simply copied the report, added the "OnOpen" code as you all suggested, updated my buttons to direct DoCmd to the new form and all works as it should. I appreciate all of the support, and I should be good to build-out as I need with a...
  14. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    When I comment out the code lines (If statement, if to end if), I get the same error. When I also comment out the "Private Sub..." and "End Sub" line I can open the report without an issue.
  15. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    Ayyy. So it threw the same error. I decided to create a new form, and add a new button. When I clicked to add the new button, I received: "The code contains a syntax error, or a CApplication function you need is not available. If the syntax is correct, check the Controls Wizards subkey or the...
  16. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    So, I have this on my Form: Private Sub Button_PrintSummaryProductLevel0_Click() DoCmd.OpenReport "Rpt - SO by Product", acViewPreview, , , , "Level0" End Sub And this on my Report: Private Sub Report_Open(Cancel As Integer) If OpenArgs = "Level0" Then Me.Section(0).Visible =...
  17. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    So, it's the code I added in the Report that is preventing it from moving forward... I'll work to clean that up
  18. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    I didn't want to pass True or False because ultimately I will have multiple buttons (producing a variety of different 'versions') for the report output. I figured passing Level0, Level1, Level2 was a more scalable option for me. I'm not even able to get to sorting out my concatenation on the...
  19. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    Thanks for this suggestion; it makes sense to me. I figured I'd do "Level0" and "Level1" in the OpenArg and then do if statements in the Report on Open. However, I gave it a try and am now hitting up against a Run-time Error '2501': The OpenReport action was cancelled" on clicking the button...
  20. D

    Solved Use two buttons to print the same report where one prints the detail section ... Freezing my application

    Here is the corrected, updated code. I pasted a version I had been playing around with. Private Sub Button_PrintSummary_Click() DoCmd.OpenReport "Rpt - SO by Customer", acViewPreview, "", , acDialog Reports![Rpt - SO by Customer].Section(0).Visible = False End Sub
Back
Top Bottom