mrchaos101 wrote: > > I am confused then... cause if you go to that AppDP it says right there: > > > > Additional Comments > > > > Enterprise edition > > > > Had to do the following: > > > > $ winetricks msxml3 > > $ wine /path/to/setup.exe > > That's just one person's test report. I've never been able to reproduce the problem, but a couple of people have reported needing native msxml3 to install. I suspect the people who report needing native msxml3 may be installing a version that is already updated to SP2 (mine isn't) and they are running into http://bugs.winehq.org/show_bug.cgi?id=18376 (One of the problems with trying to give advice on installing Office is that there are many different versions of the installer.) My suggestion is you follow the official howto first (which calls for a clean wineprefix and no overrides), and if that doesn't work, try native msxml3. > So is it my understanding that Office Access 2003 will not work very well? What if you have an app that has custom VBA code? I thought you were asking about Access 2007; that's the entry I referred you to. I've never tried to run Access 2003. My testing of Access 2007 was very limited--just enough to get it running. It seemed buggy to me, but I'm also not that familiar with it. I don't have a clue about custom VBA code; try it and find out.
