Selected Test Results (selected in 'Test Results' table below)
What works
Creating new DB, tables, forms, reports.
Opens normally existings databases with forms, ok to change data. Queries (and SQLs) work fine.
Macros quiery lists work well (did well adjusting 4900 entries on different quieries adding some other hundreds of lines to tables).
What does not
Got problems with some VB things when managing form design (eg, shows ok-error-message "unable to load dll"
when creating button - but you still can manage button-functions like
move forward, open form etc.).
What was not tested
Collaboration stuff (didn't install sharepoint things). Data connection between office applications. External links etc.
Additional Comments
Set it to bronze because of not full VB support. Is good for normal use. Might have problems if you need to add some complex macroses. Very important to read bug 19297 last comments.
Currently, Access will install but not start up (bugs 18889 & 19297). There are two known workarounds (tested in 1.1.33):
Workaround 1:(preferred method, as it does not remove any dependencies)
Use a resource editor to extract the manifest from ACEDAO.DLL (you will find it in the same directory as msaccess.exe). (I used Resource Tuner; it has a free trial and runs well under Wine.)
Save the extracted manifest as acedao.manifest in the same directory as msaccess.exe.
Delete or rename the ACEDAO.DLL located in that directory. (There is another copy in another directory--no need to change it.)
Workaround 2: (use only if there is no ACEDAO.DLL installed anywhere)
Open the file msaccess.exe.manifest (you should find it in the same directory as msaccess.exe) in a text editor.
It is NOT necessary to install vcrun2005 with winetricks or copy the dlls to the program directory.
Note that these workarounds are just to enable Access to start; functionality appears to be limited.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
Program not running
by Morten Krøyer on Monday March 1st 2010, 2:33
Trying both of the workarounds MSACCESS.EXE still refuses to run. Applying first workaround gives no effect, second workaround gives a different error message.
First error is (i'll try to find the full text later) something about the c runtime environment.
applying the second workaround makes a wine -popup telling me that MSACCESS.EXE has encountered a serious problem and need to exit.