visual basic - dao350.dll missing

david stradling

I have used a PDW to put my program on a cd. (written in VB6). On some machines, as soon as you try to run the program you get runtime error 91 signifying that a routine is missing (dao350.dll). I have been told that the solution is to change the "connect" property for the data control to Access 2000. On my version of VB this is not possible because selection is via a drop-down list. If I try to force it I get an error ISAM not loadable. If I use the PDW under visual studio, which is too basic, I can produce a cd which works. However, it does not have autorun and the database location has to be specified by the user - too complicated. I need to know what PDW to get in order to be able to produce a cd which works - any help would be appreciated.

Apr 11 '07 #1

iburyak

1. You can create a package for program distribution this way all necessary DLLS would be provided with it. Use “Package and Deployment Wizard” from VB Tools. This is recommended approach for all VB program distributions. Put package on the network and do installation on each machine from this package.

2. You can try to put necessary DLL from your machine in the same folder where your VB executable and it might help. Sometimes you need to Register this DLL on local machine.

3. You can download MDAC 2.8 from Microsoft site for free and install on local machines.

http://msdn2.microsoft.com/en-us/data/aa937730.aspx

4. Installing Microsoft Office on machine might help. It is also installs database drivers but no guarantee that it would be the same version used in your application.


Good Luck.
Hope it helps.
Irina.

Apr 11 '07 #2

iburyak

I have used a PDW to put my program on a cd. (written in VB6). On some machines, as soon as you try to run the program you get runtime error 91 signifying that a routine is missing (dao350.dll). I have been told that the solution is to change the "connect" property for the data control to Access 2000. On my version of VB this is not possible because selection is via a drop-down list. If I try to force it I get an error ISAM not loadable. If I use the PDW under visual studio, which is too basic, I can produce a cd which works. However, it does not have autorun and the database location has to be specified by the user - too complicated. I need to know what PDW to get in order to be able to produce a cd which works - any help would be appreciated.

Is it possible that when you created your package you didn't mention to add DAO and if you did will it register this DLL on local machine?

Apr 11 '07 #3