From: kheb1999@...
Subject: thanks to your Stupid help
Message:
did you read what i wrtoe before you answer me man
i said Database provider Error and i didin't said database file not found
check Error No. before you answering and please when you dosn't know know don't answer to anyone
I started off with this is probably a daft question didn't I?. Error 3706 can mean anying thing from Jet not installed, to MDAC not right or not present, to a malformed connection string.
Not being stupid like me , you'd know that wouldn't you?
Also you are aware that deploying vb apps are very sensitive to dll versions and that deployment wizard can be very bad for stepping between dll versions.
Now do you want some f'ing help, or do you want to take your ignorance out on me.
What operating system are you deploying to and which one are you deploying from.
MDAC used to have a perennial problem with breaking when you upgraded it, ending up with a dll mismatch that wouldn't work with anything. Though from your description it was weither already broken or your VB app was expecting a different one.
MS used to provide a tool to tidy it up.
You could also try installing mdac on the target machine with mdac_typ.exe, which is meant to do the job properly.
When you are looking at solving a fault like this, the first thing you do is cut out the easy and obvious.
Seeing as I'm not f'ing psychic I started at step 1!
You might want to work on your people skills, you also might want to remember people in the middle of attempting to solve a problem make all sorts of assumptions about what they've obviously tried, because of their obvious skills and experience.
So they post questions like
"This doesn't work Help" and the first thing you have to ask to help, is what doesn't work.
If you are going to insult me any more at least have the bottle to do it in public.
