FOUND IT!!
MSDERUN.DLL
When I originally used the Package and Deployment wizard, MSDERUN.DLL wasn't
included (it SHOULD have been). W95, W98 and W2000 in succession in the last
couple of years, didn't give a damn, and I didn't know it was missing -
everything worked!!
First installation on an XP machine about three months ago - no DE reports.
(error 713).
Find out about it on Google. Lots of others reporting this error as well.
Microsoft had the error on ID248055, but their fixes didn't fix it. It did
mention the MSDERUN.DLL, though.
I checked the "support" files on both deployment packages and it showed
MSDERUN.DLL was not included in the support files.
P&D again, and I manually included MSDERUN.DLL (but from the C:\windows\system
folder). Bells should have gone off then, because it responded with a "no
dependancies" message, and I added it with no dependancy info.
(Then forgot about it)
No, still not working
After several weeks of trying other fixes, one of the long-shot fixes I tried
was to register MSDERUN.DLL. Nup!!
It wasn't until I re-packaged another program today (which DID include the
MSDERUN.DLL) and installed it on my XP, that the "Run time error 713" went away.
OK - back to problem child. Run the P&D and re-install. Nup!!
I re-ran the P&D on the working package and noted where it was sourcing
MSDERUN.DLL.
When I re-ran the P&D on the faulty package, I manually added it, using that
(Correct?) source..
This time I didn't get a "No dependancies" message.
After installation on the XP, the program was working properly!!!
Bugger!!
That will teach me not to pick files out of the system folder in future
(But why didn't the P&D automatically grab it from the right folder in the first
place, five years ago?)
Argusy
Dikkie Dik wrote:
Dependency walker is part of visual studio (and can be downloaded as
well). That utility shows which DLLs your compiled application uses.
Best regards
argusy wrote:
I've already had that problem. changing my code to use Jet4.0 instead
of Jet3.1 when accessing an access database fixed that.
If that fixes your problem, then you may get another if you're using
datareports
Now, if I could only find which visual basic .dll that's NOT installed
with XP, I might fix the datareport problem....... (which, btw,
appears as error 713)
The microsoft MSDN fix? .... doesn't....
BUT, VB installed over XP - problem disappears.
SO... install VB on 26 XP computers?
don't think so - I've only the one licence
Argusy
Dave wrote:
I created a program using VB6 under WIN 98. The program uses an ado
database.
When I use the package and deployment program in VB6 on this program
and then install it on a machine with XP Pro on it, I get the Provider
can not be found error..
Any Ideas....I Hope