I am developing an app done mostly in MSAccess and need to
use ODK for distribution.
There are a couple of small VB exe's that go with it, so I
included these along with MSVBVM50,DLL in the ODK setup.
Seems to work fine on all tested platforms, but now one user
says it won't run the VB stuff. Error message can't find
the DLL
I don't understand how this can happen.
Problem is, this is all a bit new to me.
The name of the DLL suggests it has to do with virtual
memory.
Is the version of the DLL OK or will it give problems
if the ODK setup tries to overwrite an earlier or later
version?
Can I or should I force the registration using regsvr32.exe
which apparently registers a DLL.
It seem that using the VB install setup might solve these
problems, but is it worth it for just a small VB exe.
I've also heard thast the VB setup (or PD wizard) gives
more problems than it solves
Does this mean that a VB exe isn't truly portable?
My stuff: Win95, VB5, Office97 ODK
If you've got this far then thanks for your perseverance.