Microsoft Access
From Wine-Wiki
Microsoft Access is the database in the well-known Microsoft Office Suite. Commercial companies may prefer the Codeweavers commercial version of Wine which provides support for Microsoft Access. They have funded large sections of the development on MS Office and Wine and apparently allow you install as easily as on Windows.
Because Access allows extensive access to programming, some methods do not appear to work on wine. Bug reports with small examples would help wine.
This wiki is mainly collecting unofficial tips and suggestions from the forums and does not replace the application database.
Contents |
Wine application database
This Software is listed in the Official Wine Application Database
Winehq Main AppDB entry Access
- Winehq AppDB entry Access 97 no test results. needs several maintainers.
- Winehq AppDB entry Access 2000 old test results. needs several maintainers, and needs users to log onto bugzilla to confirm bugs reported.
- Winehq AppDB entry Access 2002/XP old test results. needs several maintainers
- Winehq AppDB entry Access 2003 old test results. needs several maintainers, and needs users to log onto bugzilla to confirm bugs reported.
You can help development by simply confirming whether you too experience a bug that has been reported. This will tell a developer that it is a real bug.
as of mar 09 Access does not yet run reliably and it can corrupt the databse when it crashes. if you are testing make a backup of the db every time you change it. Some simple stuff works fine, some does not. More tests are needed. Attaching to bugzilla simple databases which highlight specific bugs may help. More users checking bugs reported and confirming whether they occur, as well as checking for regressions would make a difference.
- Can you add your results to the Official Wine Appdb? Submitting your results for this software under Wine will help the many other users who run Wine.
| |
Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release.
Official Information Unofficial Information A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help. Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it.
Further Help to Wine |
Codeweavers App Entries
- Codeweavers App entry Access 2003
- Codeweavers App entry Access 2000
- Codeweavers App entry Access 97
Current Status
- Further Details currently Unknown
Access 97 with default Ubuntu Hardy Wine package (1.0.0)
[Mar 09] ms access 97 from the wine user mailing list: The only thing I did was to use the work around to install Access by forcing a few dll to be native microsoft ones instead of wines built in ones. ole32.dll, oleaut32.dll, olepro32.dll, rpcrt4.dll, stdole2.tlb and stdole32.tlb all were set to native override. [stdole2 and stdole32 are not listed - he Typed them in the winecfg droplist box]. That got Access 97 installed without the error popping up at the end of the install. Then odbc32.dll and odbccp32.dll got set to native after that to make wine let the ODBC drivers from windows.
A user noted: by removing some install options (e.g. calendar) the install worked fine without those overrides. I made those dlls native override except for the last two (stdole2.tlb and stdole32.tlb) which do not exist in the overrides droplist. [Ed please submit results to the appdb. More testing and filing bug reports would help wine]
[Sept 08 - unknown wine version]
- Installs without actual problem, only those details:
- When you choose custom installation, navigation into the components is buggy: when you click on the list, it does not select the item under your mouse pointer but only gives the focus to the list.
- When it is installed and you want to re-run the installer, loading "autorun.exe" does not work, you have to use install.exe.
- When installed, it start without problem, but some of my databases do not work (VBA).
Ed: Excellent news! Please submit these test results to the official Wine application database page for access 97
Mailing List Comments
Tips and tricks
Testing Wine and Access
Because wine progresses so fast, tips about required dlls may become quickly out of date. While this program will need multiple maintainers to test it adequately, even one person as a maintainer merely occasionally submitting tests to the application database would make an important difference.
March 2008: In the past Winetools was often used but is now out of date. These days, use Winetricks to install vbruntime, dcom98, richedit30 but only if they are needed.. Some have reported success in using access on wine but because of the complexity of databases, this would likely require careful evaluation for each and every database. With problems entering the install key, one report suggested installing microsofts richedit30.exe [1]
Now before you start, remember Do Not run wine as root. Do not run wine on a windows partition. Simply put, doing that will seriously break things. Wine pretends to be a Windows Administrator, so you do not need to run as root. Now we have that out of the way, lets start our tests on a clean .wine folder (Here is a hint of one way you might do this, rename the folder you currently use say from .wine to .oldwine. Rather than starting from scratch, we can keep a backup of your last install.
- mv .wine .oldwine
update wine so for fedora.. (you will want to try on the latest wine version - see Installing Wine)
- yum update wine
and run winecfg to create a shiny new clean .wine folder in your home directory. Click Ok to close winecfg
- winecfg
Attempt to install again with and without the known workarounds, deleting the .wine folder each time. Put the compact disk in the computer and either double click on the setup.exe or type on the command line as a user
- wine <path to ms office cd>/setup.exe
Because it is a temporary testing folder we can easily start from scratch by running
- rm -rf .wine
and once again using winecfg to create a shiny new clean .wine folder in your home directory for the next test. Click Ok to close winecfg
After installing - we want to test it using a copy of your database. If something broke since your last test, then submit a bug report (even better, if possible try using Wine Regression Testing to identify who broke it). Either way, make sure you submit your results to the application database. If you must use an older version of wine, revert to the old version of wine, delete the trial .wine folder and then revert to the old fake wine system by renaming the .oldwine back to .wine. ((Another method is to use separate wineprefixes, see advanced installing wine information) If needed, use Winetricks to install windows dlls or copy dlls across from a windows install and paste them into the directory where access is, or into wine's system32 folder. While you can also use the command winedlloverrides as mentioned in this wiki and in wine documentation, winetricks is very handy and quite easy to use.
Ed. aug 08 update, running wineprefixcreate is apparently unnecessary, as recent Wine apparently will do this for you.
if clicking on the access icon on the desktop does not work This is where you run it from a terminal. install, backup your wine and create a clean wine. Once again, remember Do NOT run wine as root! With access this can be even more dangerous than usual as some access vb programmers are pure beginners and may do some seriously bad stuff. So as a user...
lets try running it from it's directory on the command line. cd to the dir,
- cd .wine\drive_c:\Program Files\Microsoft Office\Office10
- wine MSACCESS.EXE
Watch the command line for some tips. search on the errors that you see. dont forget a fixme message is usually not a problem, unless it is connected with the crash, so look more for errors such as unimplemented just before the crash, or dlls missing, and then
- a search google and this wiki for some ideas about debugging, running traces etc
- b. search bugzilla for the error messages and if it is new, file a bug.
- c. post on wine-users forum showing the errors on the command line and link it to access..
- d post your results in the access db, and you are welcome to detail how you did it here..
Dont forget to give them not only the version of access you tested, but also the wine version and any dll overrides.
oh, and to revert to the old wine (as long as you have not made any strange stuff in wine) These two commands should get you there..
- rm -rf .wine
- mv .oldwine .wine.
A user reported[Nov 05]: Wine was installed automatically when I installed suse. When I try to run access (I installed in on the c:\access drive/directory, it crashes with the following message:
fixme: font: SetMapperFlags (0x188, 0x00800000:stub - harmless
Note: from the konsole, I entered: wine e:\\access\\msaccess.exe It starts access but locks up with the licencing threat window.
J. von Thadden: You are starting Access from a native patition. This is the same as starting it under windows without installing it just from a copied directory of a friend. [...] Try to use a tool like WineTools to *install* Office/Access under Wine. wine archive
A user reported [Nov 05]: When i use ole32.dll native library i get this:>
fixme:font:SetMapperFlags (0x224, 0x00000001): stub - harmless wine: Call from 0x774fe878 to unimplemented function KERNEL32.dll.GetModuleHandleExW, aborting
wine: Unhandled exception (thread 0009), starting debugger...
R. Klazes Only native ole* dll's from Win9x can be used.wine archive [Ed when using dcom98, make sure to set wine to windows 98 using winecfg ]
- Further tips are Unknown. Feel free to add them here
Troubleshooting
- Feel free to add suggestions here, but remember to add to the application database. If you can, please become a maintainer for this software.
Access97
> Microsoft Access couldn't find the file "C:\windows\system\system.mdw". This file is required for startup.
One User reported: During install, it complains about not being able to update the workgroup database, but the install completes fine anyway. When I navigate to Access's folder and type "wine MSACCESS.EXE", the splash screen comes up just fine, then a second later, I get [the above error dialogue box. This file has something to do with Access's workgroup (tee hee) functions. I tried touching the file and setting it to 777, also tried copying system.mdw from a "real" Windows > machine, but both of these solutions ends up with an out of memory dialogue on launch. It's progress though, I got a *different* error.
J. Schaible there is a utility installed in the access directory to switch and create new workgroups. Other system.mda's won't work, since they are created individually for your system at installation time. Try to run this tool and create a new one and switch the access system to it.
The User:I found the Workgroup editor thing: c:\windows\system\wrkgadm.exe and ran it, set up a workgroup. However, when it went to save the file, I got a useful Microsoft error: "An error has occurred at changing workgroup database". The file was not created. [He then said] It's not a permissions error. Wine Archive Link
Links
