Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. cswosu

    Using string passed to function in DLookup criteria

    Thank you, sir. That is just what I needed.
  2. cswosu

    Using string passed to function in DLookup criteria

    I can't get DLookup to use the RateCode string that was passed into the function in its criteria. The RateCode is a letter that corresponds to a certain rate schedule in RateTable. It is ignoring it for some reason. What am I doing wrong? ****** Public Function...
  3. cswosu

    Populating a text box from a combo box

    Got it fixed now. Thanks for the help.
  4. cswosu

    Populating a text box from a combo box

    Ken, Here is what I have in the After Update field of FIN [Facility Common Name] = FIN.Column(1) Thanks.
  5. cswosu

    Populating a text box from a combo box

    Ken, Still got the same macro error message.
  6. cswosu

    Populating a text box from a combo box

    Ken, Here are the details of my combo box: Name - FIN Control Source - FIN (in table Release Data Tbl) Row Source - SELECT [Facility Common Names].[FIN], [Facility Common Names].[FCN] FROM [Facility Common Names] Bound Column - 1 And the details of the text box I want to change Name -...
  7. cswosu

    Populating a text box from a combo box

    Ken, I'm trying to do something similar to this in a form, but whenever a try to put "txtBox = cboMyCombo.Column(1)" in the After Update line of the combo box, Access adds extra syntax to the line and it doesn't work. Any ideas? Thanks.
  8. cswosu

    VB code works in subform, but not in main form

    Ken, Just got it to work. Had to change my DLookup line from idTest = DLookup("[Vents To]", "PSV Data", "[Tag Number] = Forms![PSV Release Subform]![PSV Number]") to idTest = DLookup("[Vents To]", "PSV Data", "[Tag Number] = [PSV Number]") Guess I didn't need that extra stuff in there...
  9. cswosu

    VB code works in subform, but not in main form

    Ken, I put a break in the code so I could step through it. It seems that it is jumping from the DLookup line straight down to "MsgBox Err.Description" near the end of the code. Any ideas why it would trip up on the DLookup like that? I'm going to keep digging. Thanks again for your help.
  10. cswosu

    VB code works in subform, but not in main form

    Ken, Sure thing. Here's the rundown - I open form "Release Calculation Form". "PSV Release Subform" exists as a subform in this form. I fill in all the relevant data in the form and subform, click the command button in the subform in order to open a report, and get the "canceled operation"...
  11. cswosu

    VB code works in subform, but not in main form

    Ken, Thanks for the quick response. I'm sorry to report that the code substitution didn't work. I still get prompted for the value of "Parent.[Record No]" in the subform, and the "canceled operation" message in the main form. Any other suggestions?
  12. cswosu

    VB code works in subform, but not in main form

    Hello all. I just found this forum; hopefully someone can help me with a problem I'm having. I have a command button in a subform with VB code that executes upon clicking the button. The point of the code is to check a value on a table and determine which report should be opened. I'll post...

Part and Inventory Search

Back
Top