As far as I can see, it is not possible to run in Wine Ms-Access-applications containing VBA code.
In most Ms-Access applications some code is written in this Visual Basic for Applications (VBA)
Is there a solution for this? Who knows more?
Bart
Ms-Access but no VBA?
-
lahmbi5678
- Level 7
- Posts: 823
- Joined: Thu Aug 27, 2009 6:23 am
Re: Ms-Access but no VBA?
It might also depend on the MS Access version. Please create a minimum testcase and file a bug.
Re: Ms-Access but no VBA?
Thanks for your reply.
Because this forum does not accept attachments with the extensions accdb and accde, you will find two examples here:
http://www.bartkuijer.nl/test.accdb and http://www.bartkuijer.nl/test.accde
This have to show a form with a button. Clicking on the button has to give a messagebox with the message " Hello; this works in Wine!"
Hope this will help.
Bart
Because this forum does not accept attachments with the extensions accdb and accde, you will find two examples here:
http://www.bartkuijer.nl/test.accdb and http://www.bartkuijer.nl/test.accde
This have to show a form with a button. Clicking on the button has to give a messagebox with the message " Hello; this works in Wine!"
Hope this will help.
Bart
-
lahmbi5678
- Level 7
- Posts: 823
- Joined: Thu Aug 27, 2009 6:23 am
Re: Ms-Access but no VBA?
Hi,
did you follow the instructions in appdb to install your MS Access? Which version? Some appdb entries mention overriding oleaut32.dll for Access, i.e. copy the dll from install medium (or maybe WinXP) to wine's system32 directory, set an dll override in winecfg to "native, builtin" or run something like "WINEDLLOVERRIDES="ole32aut=n" wine yourapp.exe".
The usual generic advice would be to upgrade to latest wine, run from command line and post terminal output. If there's no obvious error message, file a bug. It is your issue, so it's up to you to create the bug report.
did you follow the instructions in appdb to install your MS Access? Which version? Some appdb entries mention overriding oleaut32.dll for Access, i.e. copy the dll from install medium (or maybe WinXP) to wine's system32 directory, set an dll override in winecfg to "native, builtin" or run something like "WINEDLLOVERRIDES="ole32aut=n" wine yourapp.exe".
The usual generic advice would be to upgrade to latest wine, run from command line and post terminal output. If there's no obvious error message, file a bug. It is your issue, so it's up to you to create the bug report.
