Results 1 to 8 of 8
  1. #1
    New Lounger
    Join Date
    Mar 2004
    Posts
    11
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Report doesn't run (VB6)

    (Edited by HansV to provide link to post, and to indent using <!t>[tab]<!/t> tags - see <!help=19>Help 19<!/help>. Also removed superfluous line ends - the browser will wrap lines automatically.)

    I have a report which runs fine on the machine on which the program was developed but when packaged and installed on another machine I get: 'Run Time Error -2147220992 (80040200). Provider cannot be found. It may not be properly installed.'

    The report is associated with a Data Environment and the associated code is:

    Private Sub mnuFileReport_Click()
    If deEnvName.rsRecSet.State Then 'If open, close for update
    deEnvName.rsRecSet.Close
    End If
    deEnvName.rsRecSet.CursorLocation = adUseServer

    rptReportName.Show
    End Sub

    I am a beginner and have struggled to get this far. I have searched the lounge and find this is similar to <post#=144694>post 144694</post#>. However, the link with the answer doesn't work any more.

    I assume a program that is on my machine doesn't exist on the target machine and is not being included in the installation package.

    Thanks in anticipation.

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

    Re: Report doesn't run (VB6)

    You can download the free MDAC Component Checker from Microsoft and use it to determine your configuration.

    If necessary, you can download the latest version of MDAC from Data Access and Storage Developer Center.

    And it might help to install the latest version of the Jet Engine - see How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine.

  3. #3
    New Lounger
    Join Date
    Mar 2004
    Posts
    11
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Report doesn't run (VB6)

    Thanks for the speedy reply.

    Done that, no change.

    Noticed a couple of things:-
    1. During package build there was reference to Jet2.x drivers even though 4.x had been loaded as you suggested
    2. In the PDM file that is produced, MSCOMCTL.OCX is stated to have Out of Date Dependency Information.

    Regards,
    John

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

    Re: Report doesn't run (VB6)

    Jet2.x? That's an extremely old version. Check Project | References..., and make sure that there is a reference to the Microsoft Jet 4.0 Object Library, not to any 3.x, 2.x or 2.x/3.x versions.

    Perhaps you also need to install the latest service pack for Visual Studio 6 - see Service Pack 6, This should ensure that the version information in Mscomtcl.dep corresponds to the installed version of Mscomctl.ocx.

  5. #5
    New Lounger
    Join Date
    Mar 2004
    Posts
    11
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Report doesn't run (VB6)

    Downloaded and installed SP6.

    Looked at Project|References and the only Jet to be seen is 'MS Jet & Replication Objects 2.5 Library' and that is not ticked. No other references to Jet. Should I browse to find the file(s)?

    Regards,
    John

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

    Re: Report doesn't run (VB6)

    If you clear the reference to 'MS Jet & Replication Objects 2.5 Library', can you still compile your application?

  7. #7
    New Lounger
    Join Date
    Mar 2004
    Posts
    11
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Report doesn't run (VB6)

    It is not set, only in the display of unchecked items.

    Regards,
    John

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

    Re: Report doesn't run (VB6)

    Sorry, you already mentioned that. But in that case, I don't understand why there is a reference to Jet2.x during the package build process.

    I'm afraid I have no further ideas.

Posting Permissions

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