Re: ADO error (80004003) on 1 machine

mingleeshop@xxxxxxxxx wrote:
We have a C++ application developed using .NET 2003 with access to
Microsoft Access. It was working fine for a lot of machines until
recently on one of our customer's machine. It failed during the call
to CreateInstance().


This may help as well:
http://www.google.com/search?hl=en&lr=&q=80004003+Jet
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"


.

Relevant Pages

  • Re: Problem with Standard Functions
    ... Are they all sharing the same database, Mark? ... Doug Steele, Microsoft Access MVP ... > As the machines acted up I removed library references which initially ...
    (microsoft.public.access.formscoding)
  • Re: Problem with Standard Functions
    ... > Are they all sharing the same database, Mark? ... I think I tested that on one of the machines, but will again when the users ... >> Microsoft Access 10.0 Object Library ...
    (microsoft.public.access.formscoding)
  • ADO error (80004003) on 1 machine
    ... Microsoft Access. ... It was working fine for a lot of machines until ... Here's the code snippet: ... LPTSTR lpstrConnection = ...
    (microsoft.public.data.ado)
  • Re: ADO error (80004003) on 1 machine
    ... The error code= 80004003 ... Microsoft Access. ... It was working fine for a lot of machines until ... This email account is my spam trap so I ...
    (microsoft.public.data.ado)
  • Developer CD - 2003 compatibility of Access 2000
    ... My organisation is currently using Microsoft Access 2000. ... We wish to deploy some databases on machines that do not have Access ... installed using the runtime version capability. ...
    (microsoft.public.access.gettingstarted)