Results 1 to 5 of 5
  1. #1
    New Lounger
    Join Date
    Oct 2002
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Access 2000/2002 Compatability (2000/2002)

    I have a an access db connected to a SQL Server 2000 back-end via odbc. I have a mixed environment with users running the .mdb file locally on Office 2000 and OfficeXP workstations as well as users connected through a Citrix box running Office XP. When a major design change occurs, I have code that copies down a fresh copy of the .mdb file from a central server to each local workstation. I sometimes make design changes via Citrix and then recompile and compact/repair the .mdb file before making ready for distribution. I am getting unpredictable results on the local workstations, sometimes crashing Access all together. I have added the 9.0 library references to the Citrix box so that the references are not inadvertently changed causing errors on the local 2000 workstations. There are approximately 35-60 users using the application at any one time. Does anyone have any suggestions how I might make the application more stable? The application has provided 3+ years of very stable service in Access 97.

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Access 2000/2002 Compatability (2000/2002)

    Are you doing development in Access 2000 or 2002? Have you explicitly declared data access as DAO in all cases where you are manipulating recordsets via VBA, or recoded to use ADO? Did you convert your database from 97 to 2000 or 2002, or did you import objects into a new empty database? We've seen all of these situations cause some grief. In particular, in one situation we developed a database in 2002, but using 2000 format, took it to a "clean" 2000 PC, and it would crash every time. Simply importing all the objects into a 2000 database on the 2000 PC solved the problem <img src=/S/bagged.gif border=0 alt=bagged width=22 height=22> ! We've also seen situations where different versions of the MDAC used with the SQL Server ODBC driver would cause weird things on specific PCs. And finally, converted Access 97 databases occasionally display bizzare behavior. The good news however, is that once you resolve those kind of issues, 2000 is significantly more stable than 97, and 2002 is even more stable.
    Wendell

  3. #3
    New Lounger
    Join Date
    Oct 2002
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Access 2000/2002 Compatability (2000/2002)

    Thank you for response. Actually the application has all of the characteristics you have outlined. The application was created in Access 2000 and all of the objects imported from the Access 97 database. Then I revised the code that prevented it from being compiled and changed references to the office assistant that were no longer available in Access 2000. I have not implicitly declared data access as DAO in references to a recordset (which I will do now), but did change the order of the library references in the tools menu of the module design window after having strange problems with recordsets. Although most of the development is done on a 2000 only machine, some development does happen on an XP machine, and this has caused some problems in library references. I will check the mdac version on some workstations. can you make any suggestions re: best practices for distributing a local application so that each client workstation has all of the libraries, mdac version, files, etc. needed to run the application. Thank you

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Access 2000/2002 Compatability (2000/2002)

    <hr>can you make any suggestions re: best practices for distributing a local application so that each client workstation has all of the libraries, mdac version, files, etc. needed to run the application.<hr>
    The only way to do that is with the developer's edition and creating a setup that will install the necessary files on each machine. If you're using Citrix, of course, it's a different situation entirely.
    Charlotte

  5. #5
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Access 2000/2002 Compatability (2000/2002)

    One suggestion is to try to do as much development as you can on 2000, and where you have to do it on XP, then import the object into your 2000 version before you distribute it. A less complete solution than the one suggested by Charlotte is one we developed which downloads various components to each workstation as changes are made. If you want further info about it, check out our web page or email me.
    Wendell

Posting Permissions

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