Hi Craig,
I've seen that error message before from graphical programs which require root privileges to run. Even if you start the program as root from a command prompt (while logged into kde as a non-root user), it doesn't work. I'm sure that it's possible to code X programs which resolve this situation without the error, but this program certainly isn't the only one to do it this way.
The solution is to generally start a new X session as root, ie; log out of kde, and log back in as root. Then run the program again. Presumably this is just the installation/setup stuff, so that it should run normally the next time you use it as a regular user.
btw, I'm using Crossover office here and it works quite well. I haven't tried access, but it certainly works with the latest version of IE, and with MYOB Accounts.
... I haven't followed the whole thread completely but at least the above is not only wrong, it shows that you have little or no sense of security at all, which is even worse! Sorry to be so blunt, no offense meant. It's just that advices like the one above from you is the way to make a secure operating system insecure. And even worse, it hurts the reputation of Linux to be a secure operating system. To cure the situation of logging in and programs started as root having windows opened is pretty easy. There are basically four ways to do this. Instead of starting an X session as root, which basically puts the whole system into jeopardy by opening X services that an attacker can use to gain access to your machine and/or destroy your system, log in as a normal user. Then open a shell window and do the following: 1. The "sux -" method This is definitely the best way to do it on the _local_ host. It is pretty much the same as "su -" but with the addition of letting programs run by root open windows on your display. 2. The "xhost" method technically possible but HIGHLY insecure! DON'T!!! Do an "xhost +localhost", then "export DISPLAY=:0.0" and then start your program. You will be prompted a message that reads: "localhost being added to access control list" This will allow all programs on your local machine to open windows on your local display. Note: This is also, tho _somewhat_ limited, a security hole! 3. The "xhost" method, second edition technically possible but HIGHLY insecure! DON'T!!! To make point 2 even worse you can even do an "xhost +" instead of "xhost +localhost". Note that this will allow _ANY_ host to exploit your X server's security holes! This is pretty much like opening a few vital things in your firewall. And we don't want that, do we? ;-) 4. The "ssh" method Use "ssh -X root@localhost". This is just as secure as the "sux -" method described above. The "-X" option makes sure that you can start programs that open windows on your display. If you leave the "-X" option out then you get the same error message as if you would have done "su" or "su -" Believe me, it's either method 1 or 4 that you want but definitely NOT methods 2 and 3! 2 and 3 both will give attackers a good chance to compromise your system! Also _NEVER_ use the graphical login to log in as root or start a new root X session any other way. Simply _NEVER_ start a root X session at all! Everything can be done thru a shell window using either of the above methods 1 and 4. Hope this clears matters up a bit. -- cul8er, Paul paul.foerster@gmx.net