Results 1 to 4 of 4

Thread: Runtime 2467 only on a Win 7 Machine

  1. #1
    ilikebirds is offline Novice
    Windows 7 64bit Access 2010 64bit
    Join Date
    Jun 2012
    Posts
    14

    Runtime 2467 only on a Win 7 Machine

    For the following code I'm getting a runtime 2467 expression not available error only on my Windows 7 machines.

    Me.Browse.Form.Filter = strWhere

    I am completely lost as to why.

  2. #2
    Rawb is offline Expert
    Windows XP Access 2000
    Join Date
    Dec 2009
    Location
    Somewhere
    Posts
    713
    I'm gonna be honest. I'm not familiar with the "Browse" Object and, because Google it horrible for "technical language" searches, haven't been able to find anything on it...

    Can you give me more info on what it's for?

  3. #3
    ilikebirds is offline Novice
    Windows 7 64bit Access 2010 64bit
    Join Date
    Jun 2012
    Posts
    14
    [Solution] "Browse" was just a FORM name. The actual code looked like this:
    ==================
    If Title
    If Nz(Me.Program) <> "" Then
    ' Add it to the predicate - match on leading characters
    strWhere = strWhere & " AND " & "MainDB.Programpre Like '*" & Me.Program & "*'"
    End If

    ' If Case #
    If Nz(Me.[CaseNumber]) <> "" Then
    ' Add it to the predicate - match on leading characters
    strWhere = strWhere & " AND " & "MainDB.[Case #] Like '*" & Me.[CaseNumber] & "*'"
    End If
    ==========

    So I slowly back tracked into why it was giving this error and when I tried to open the subform directly it gave me the OLD path of a split back-end database.
    I have no idea where this information was stored - but if anyone does know that would be useful.

    In the end what I did was go back to an earlier copy of my DB - Split it again in the right locations and then distributed out the Applications Dbs.

  4. #4
    Rawb is offline Expert
    Windows XP Access 2000
    Join Date
    Dec 2009
    Location
    Somewhere
    Posts
    713
    Ah, if Browse is the name of a Form, then you should use Forms!Browse.Form.Filter (or just Me.Form.Filter if you're executing code from within the Form) to reference it instead of Me.Browse.Form.Filter. It's (marginally) faster and there's less ambiguity in the code.

    As for your program, that's probably the easiest way to deal with it if you're not sure what Tables were linked correctly and what weren't. The Linked Table Manager that comes with Access is pretty clunky (It's the second item on the "External Data" Ribbon).

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 6
    Last Post: 09-20-2012, 03:22 PM
  2. Replies: 13
    Last Post: 06-12-2012, 08:52 PM
  3. Replies: 1
    Last Post: 10-04-2011, 01:39 PM
  4. A2007 Runtime on same machine as A2003
    By jhollingsh615 in forum Access
    Replies: 4
    Last Post: 05-24-2011, 11:17 AM
  5. Access 2007 - 64 bit Machine
    By greggue in forum Access
    Replies: 1
    Last Post: 09-28-2010, 11:42 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Tech Forums: Microsoft Office Forums