wine users - Feb 2010 - How do I debug a VB application install?

I'm trying to debug the installation of a Windows app written in VB (I think
VB6). Following the troubleshooting guide here, and referencing the app's
own install log, I realized some necessary DLLs were missing. Installed them
using winetricks mfc42 vb6run mdac28. I checked a working installation on
Windows XP for list of installed MDAC components, and I think I've got all
the necessary DLLs. The app's own install log no longer shows any DLLs
failing to self-register because of missing supported DLLs.

However, in spite of the fact that the app's install log shows no errors
(that I can find), the installer itself gives the following message at the end:

Code:
Run-time error '3706': Provider cannot be found. It may not be properly
installed.



The wine install log is as follows:
Code:
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume'
element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume'
element
err:ole:CoGetClassObject class {6c736db1-bd94-11d0-8a23-00aa00b58e10} not
registered
err:ole:CoGetClassObject no class object {6c736db1-bd94-11d0-8a23-00aa00b58e10}
could be created for context 0x1
err:ole:CoGetClassObject class {6c736db1-bd94-11d0-8a23-00aa00b58e10} not
registered
err:ole:CoGetClassObject no class object {6c736db1-bd94-11d0-8a23-00aa00b58e10}
could be created for context 0x1



And when I try to run the app I get the message box
Code:
Provider cannot be found. It may not be properly installed.

 and the app fails to launch.

The wine application log is:
Code:
err:winedevice:ServiceMain driver L"MCSTRM" failed to load
fixme:ole:CoInitializeSecurity (0x413ea8,-1,(nil),(nil),1,3,(nil),72,(nil)) -
stub!
err:ole:CoGetClassObject class {24e669e1-e90f-4595-a012-b0fd3ccc5c5a} not
registered
err:ole:CoGetClassObject no class object {24e669e1-e90f-4595-a012-b0fd3ccc5c5a}
could be created for context 0x1
wine: Module not found




I fell like I've made progress here. How can I bring this home?

Thanks, --Lee

OK, the app uses an MS Access MDB, so I figured out that JET was missing and
I?installed with
Code:
sh winetricks jet40


The app now launches successfully (yay!). Unfortunately, there are several 
features that immediately crash the application.

Probably little more that I can do, but if anyone has experience with getting MS
Access applications to run with Wine, please let me know what you've
encountered.

<<getting MS Access applications to run>>
Sounds like it is only using the Access database format accessed by the Jet
engine, you are still needing to debug the vb app itself not Access.

look at 
http://wiki.winehq.org/FAQ#head-a37de3282d447376d2220d20a278ae52258551a4
or
http://wiki.winehq.org/FAQ#head-16da35b6327024d6ea576e3678488b16862d0f5e

alternatively if you have the VB app source code and own VB you can install it
under wine and try debugging the actual vb code.