data control causes Runtime Error 91 only in Windows 2000

From: Ed Hammond (ehammond.no.stupid.spam_at_apcom-inc.com.no.stupid.spam)
Date: 05/04/04

  • Next message: david epsom dot com dot au: "Re: Long table name support ??" 
    Date: Tue, 4 May 2004 16:34:14 -0500

    This is a crazy bug that I can't figure out for the life of me.

    I developed a DAO 3.6 application on my Windows 2000/Office 2000 machine
    using VB5. The program assigns a DAO 3.6 recordset to a VB5 data control.

    The program worked fine on my computer, so I set out to deploy it to other
    machines in my company.

    It worked fine on Windows 98 machines. (after installing DCOM98 updates and
    Jet 4.0)

    It worked fine on Windows NT machines (after installing Jet 4.0)

    The datacontrol generates an error 91 on every Windows 2000 machine except
    mine. The datacontrol pretends nothing is wrong until I try to access a
    record from it. It gives no error when the code assigns the recordset to
    it, it just stays = Nothing. Of course I get an error 91 when I try to get
    data from "nothing". What's frustrating is the code has worked perfectly on
    approximately 8 Windows '98 and NT machines.

    Can somebody give me a hint on what to look for? I've played with different
    installations of MDAC already and updating 2000 to the latest service packs.

    Please help!

    Thanks in advance.

  • Next message: david epsom dot com dot au: "Re: Long table name support ??"

    Relevant Pages

    • data control causes Runtime Error 91 only in Windows 2000
      ... The program assigns a DAO 3.6 recordset to a VB5 data control. ... It worked fine on Windows NT machines ... The datacontrol generates an error 91 on every Windows 2000 machine except ...
      (microsoft.public.vb.database)
    • Recordset slow in windows xp
      ... on windows xp and 2k machines where the following code ... Creating a recordset from a querydefinition takes about the ... The debug results are just an example, ...
      (microsoft.public.access.formscoding)
    • Access 2003: Execute VBA-SQL Server Souce Code of Books Examples
      ... I have Windows XP Pro PC that is on Microsoft NT 4 LAN System. ... 'Create recordset reference, and set its properties. ...
      (microsoft.public.access.security)
    • Re: Losing recordset object with form close and docmd.quit
      ... > Try using the Quit Method of the Application object instead. ... > Windows will most like recover the resources for the workspace when ... >> the recordset I opened with code when I am in this condition even ... Sub CloseDatabaseAndAccess() ...
      (microsoft.public.access.forms)
    • Re: VB6: Which ADO version to reference?
      ... I installed VB6 on the Windows 2000 system and discovered that the ADO ... I often compile my VB apps using the 2.1 reference, ... Library"and "Microsoft ActiveX Data Objects Recordset 2.7 Library" ...
      (microsoft.public.data.ado)
    Loading