Results 1 to 4 of 4
  1. #1
    Join Date
    Mar 2015
    Posts
    15

    Answered: Problems with search form

    So, I have put up a search form, based on a querry.

    Code like this: Like "*" & [Skjemaer]![fSøk]![txtDatoSøk] & "*"

    This works perfect, except when I know put this form into my Navigation form, then the msgbox appears, asks me tu put in parameters... Any suggestions?

  2. Best Answer
    Posted by ranman256

    "this search criteria is correct (it is in criteria, right?)

    If the query is asking for params, then either ,
    it is looking for a field that doenst exist in the tables shown,
    or
    a field is misspelled, (thus the field doesnt exist)"


  3. #2
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    496
    Provided Answers: 24
    this search criteria is correct (it is in criteria, right?)

    If the query is asking for params, then either ,
    it is looking for a field that doenst exist in the tables shown,
    or
    a field is misspelled, (thus the field doesnt exist)

  4. #3
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    ...is the form fSøk open when you try to refer to it from the navigation form?
    I'd rather be riding on the Tiger 800 or the Norton

  5. #4
    Join Date
    Jun 2005
    Location
    Richmond, Virginia USA
    Posts
    2,763
    Provided Answers: 19
    Quote Originally Posted by Director View Post

    ...This works perfect, except when I know put this form into my Navigation form, then the msgbox appears, asks me tu put in parameters...

    When
    does the parameter entry box pop up?

    When the Form first opens?

    When you enter a search term and start the search?

    A Form that works perfectly, until it is placed on a Navigation Form, at which time it goes completely bananas, is almost always a victim of the fact that when a Form is placed on a Navigation Form, it (the original Form) actually becomes a Subform, and it and its Controls have to be referred to as such, with the correct syntax.

    Linq ;0)>
    Hope this helps!

    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •