Results 1 to 5 of 5
  1. #1
    4 Star Lounger
    Join Date
    Dec 2002
    Location
    Kitchener, Ontario, Canada
    Posts
    421
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Failed ADO Connection (2003)

    I am servicing someone else's very complicated database that was designed in Access 2000. It is split Front End and Back End with gobs of code running forms. One computer on the network has Office 11 installed. Everyone else is using XP. The desktop operating systems are all XP as well.

    To add a new client into the database, there is a search form that is activated that will search to see if that client already exists. If they do, the database won't let you add them in again. If they don't then you are allowed to enter them. The problem comes in the search process. First of all you get "error 2683 There is no object in this control" with OK being the only button in the dialog. When you hit OK you get taken to a confirmation form which has the info you entered into the search form listed. When you hit OK it begins the search which is where the code breaks and returns the following error: "Local error (failed ADO Connection): Click "Back" and try again". I did upgrade Jet to Service Pack 8 to no avail.

    I have checked references and they seem fine but I'm not completely sure which ones are required for ADO to function properly. Also I haven't looked really closely, but I wonder if it is more likely the original code is actually using DAO and that reference needs to be checked. I haven't done much with ADO and this is my first time even looking at 2003 so I'm a bit out to sea here about where I might look to solve the problem.

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

    Re: Failed ADO Connection (2003)

    You cannot mix DAO and ADO. If you're getting an ADO error, it isn't from DAO code. The "there is no object" error is highly suggestive of a conflict between versions. Who is seeing this error (which machines)? When did they start seeing it, and under what circumstances. What version of ADO is referenced? The default version in 2000 was ADO 2.1, which had a lot of problems. Version 2.5 was the first really stable version. All your front ends need to have the same 2.5 or higher reference set. If the code uses the ADOX object, you'll need that reference as well.
    Charlotte

  3. #3
    4 Star Lounger
    Join Date
    Dec 2002
    Location
    Kitchener, Ontario, Canada
    Posts
    421
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Failed ADO Connection (2003)

    As far as I understand, it is only the machine with Office 11 running on Windows XP that is having this problem (there are easily 15 machines on the network and only this one has Office 11. Everything else is XP). The network administrator is going to confirm this on Monday when he goes in to deal with some other issues. As the database was asking for the Jet Service Pack 8 upgrade and I have seen broken code from Jet being out of sync with Windows updates I did update to service pack 8 on this machine. It didn't make any difference.

    This problem seems to have started when this machine had software reloaded and upgraded to Office 11. As I'm coming in from outside and dealing with end users, it is difficult to get exact info.

    If I remember correctly from this morning, ADO 2.1 was referenced. I did try changing that reference to 2.7 with no change in the error message. How would I know whether ADOX is used? Will it make a difference if this one machine has a reference to a higher version of ADO in its front end than the other machines on the network?

  4. #4
    4 Star Lounger
    Join Date
    Dec 2002
    Location
    Kitchener, Ontario, Canada
    Posts
    421
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Failed ADO Connection (2003)

    Thanks for the advice. It more or less confirms my suspicions, but you give me some additional areas to check. There is no reason whatsoever in this environment for them to need Access 2003 (for that matter, they don't even need XP) to accomplish their goals. I suggested to the IT guy that the easiest solution may be to get rid of Office 11 and go back to XP on this machine. I believe there were some problems with this machine which necessitated reloading all the software or perhaps reformatting and starting from scratch and at the time the media they had was Office 11. I'm a little fuzzy on the details since I only get called for Access problems.

    I'm pretty sure there are no custom libraries or mdes. It is a very straightforward database, just very large and complicated (in some instances overly complicated!) in its design.

    Thanks again for your help.

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

    Re: Failed ADO Connection (2003)

    If the project compiles without the Microsoft ADO Ext. 2.x for DDL and Security checked, then you don't need the ADOX library, which is what that is.

    Try to make sure everyone is using the same ADO reference just to level the playing field. Version 2.7 is well tested and should behave on the XP machines. I suspect your problems stem from the fact that 2003 isn't quite as compatible with 2000 and XP as MS would have us believe. We saw similar kinds of breakage between 2000 and 2002, and I have my suspicions about 2003. If you update that machine to Jet SP8, you may have to update the others as well. In our office, we have a couple of machine with 2003 loaded, but mine isn't one of them, and we don't use it for development yet, so I can't be sure what the impact is of mixing SP8 and SP7. I believer the SP8 also installs MDAC 2.8 (or vice versa), but again, I can't say for certain. We found that the machines with 2003 installed also needed the latest service packs for Windows XP and for Office XP to keep Access XP from crashing, which reinforces the idea that the versions are not wholly compatible out of the box.

    Does the application use any custom libraries, especially MDEs? We found with 2002 that it wanted mdes in its own format. You may have to isolate that machine until you can sort out the problems, but if it has been working for the other machines, then 2003 is the likely culprit and your IT people are going to need to figure out what it takes to make it play nicely with others. <img src=/S/crazy.gif border=0 alt=crazy width=15 height=15>
    Charlotte

Posting Permissions

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