https://bugs.winehq.org/show_bug.cgi?id=52369
--- Comment #9 from Leon leon.dejong@hotmail.com --- OK, progress!
I checked the mounting and mapping and came to the conclusion that that's not the culprit. When you open an explorer (from winetricks) you get a perfect mapping (D: in my case) and can operate on all the files visible. This made me believe it's not Wine that's the issue. You would have had many more complaints from other users as well.
So then I moved on to BK. I checked if it uses any external controls for network/dialog functionality and it doesn't. There are only a few external libraries for BTrieve (the database side of the app). I went into the archives of memory lane and dusted off my VB disks and made a q&d mock up of the screen that John Steed made. And the default Drive control does the same: it shows my mapped D: drive as ] and gave me an error 76 (drive not available).
https://bugs.winehq.org/attachment.cgi?id=71609
To check whether it's really the control, I created an option with the default Windows dialog to browse for the folder. This dialog shows the correct mapping and path so the conclusion is that it's the Drive control of VB6 that doesn't pick up the network mapping.
https://bugs.winehq.org/attachment.cgi?id=71610
I'm now trying to create a function that shows the result of the default dialog under the Drive control so John Steed only needs to update the code behind the Drive control (if he'd be willing to address this issue).
So stay tuned ... :-)