If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Nope, tried it on our test machines with Windows XP Pro and Office 2003 and had no joy replicating the problem. I even tried installing it on a totally clean machine. The only thing I could possibly think is perhaps the customer with this problem and my home computer have a bad installation of Microsoft Office and it has somehow affected our software but I'm not entirely convinced.

Can this person, and others, connect to a network or a server or whatever, that you can also connect to?

My thought is this: If this type of connection is possible, could he, on his end, "clone", using something like Ghost, his entire hard drive, and put it up somewhere that you could get it? Then, in turn, you would load his hard drive image onto a machine in your shop. At least you would be able to see what he/she is seeing.

I don't answer coding questions via PM or Email. Please post a thread in the appropriate forum section. Please use [Code]your code goes in here[/Code] tags when posting code.Before posting your question, did you look here?Got a question on Linux? Visit our Linux sister site.Modifications Required For VB6 Apps To Work On Vista

Is there not some sort of program that I could install on my home machine to try and trace what the software is trying to access? FileMon wasn't too much help but I'll give it another try. the only other thing I can think of is to try and force the problem to occur by manually removing the dlls installed in the software setup to see if I can get the error to occur in the same place as the customer.

Another thing I found on the web is that sometimes a program will look for a specified dll (for some strange reason) in the application path (and not the system32 path where it actually is and was installed) and so could generate this error.

I finally managed to fix the problem. After reading what other people had said about moving certain dlls into the application path, I moved the entire contents of the ado folder in C:\Program Files\Common Files\System\ado into the program's application path and that seems to fix the problem on my home machine. Don't know why but I'll have to try and figure out which dll it is that needs to be in the application's path in order to fix the issue. I don't know why it does though!

Anyway, I'll let you know which dll it was that needs to be in the application's path and then if that definately sorts the problem out then I'll let my customer know that this is what he has to do to fix his issue

seems the msado dll was not registred, you need to "regsiter it" first in your machine so that you kan use it from any where ... normally when the application faild to find the depending "dll" it start searching in the "system32" folder and in the application folder ... when it fails all it pop up a "faild to find dll" error message ... unless the dll is registred in the system and the system knows where to find it exactly.

I would agree that it needs to be registered, but I would ask why it isn't getting registered on some machines (those with the problem) and appears to be getting registered (those without the problem) on others.

Everyone uses the same installation and setup package,right?

I don't answer coding questions via PM or Email. Please post a thread in the appropriate forum section. Please use [Code]your code goes in here[/Code] tags when posting code.Before posting your question, did you look here?Got a question on Linux? Visit our Linux sister site.Modifications Required For VB6 Apps To Work On Vista

well i think any corruption, another program installation, anything ... and of course ado doesn't come with the windows-home so maybe the ado installer .. the installer registration was corrupted in the home for any reasons ...