Results 1 to 3 of 3
  1. #1
    Lounger
    Join Date
    Feb 2001
    Location
    Upstate, New York, USA
    Posts
    47
    Thanks
    0
    Thanked 0 Times in 0 Posts

    #Error on report when launched from form (Office 2K, SP3)

    Windows 98SE

    I have a form in an Access DB that passes parameters to a query. On the form I have a command button to launch a preview of the report bound to that query. Some of my end users can launch the report with no problems; others get "#Error" all over the report doing it this way. However, on the affected machines, if I take the parameters that reference the form out of the query and hard-code actual values, the report runs just fine.

    Any ideas? If more info is needed, please let me know.

    Kyle

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: #Error on report when launched from form (Office 2K, SP3)

    If possible, check the following on one of the PC's that have this problem.

    Open the database with Shift key held down to bypass startup options (if set).
    Switch to the Visual Basic Editor (Alt+F11).
    Select Tools | References...
    If you see references starting with MISSING, note which ones they are, then clear their check boxes.
    Click OK.
    See if you can compile the project code (Debug | Compile <projectname>)
    If you encounter any errors, try to resolve them.

    Does the report work OK now?
    If not, post back.

  3. #3
    Lounger
    Join Date
    Feb 2001
    Location
    Upstate, New York, USA
    Posts
    47
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: #Error on report when launched from form (Office 2K, SP3)

    I had checked the references already - I apologize for leaving that detail out (funny how important things slip the mind...). Anyway, we've discovered that the problem seems to be stemming from a date field another user had added to the form. When he disabled that field, everything ran fine. We're working now to see why that date field bombed out on us (naming problem, perhaps?).

    Thanks for the reply.

Posting Permissions

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