Le mercredi 14 février 2007 00:MM, Shaun McDonald a écrit : > Hi Alex,
Hi Shaun, > > If I remember correctly your on Mac OS X 10.3.9, which means that > testing with the latest version is not currently an option due to > some build breakers on Mac OS X 10.3.9 and gcc 3.3. I don't think you read my message correctly. I said I'd been testing the ODBC drivers provided by Actual Technologies for MacIntel. You are correct when you say I have access to a test machine that is a PPC 10.3.9, that is the one I've been doing QA on, but it is not the one I tested the Actual Technologies drivers on. My colleague and associate (a non-tecchie, long time Mac user) has a production machine MacIntel running 10.4 with the latest security fixes. I can not use this MacIntel machine to run tests on, but I need something that works. Actual Technologies is, as far as I know, the only company to provide a binary driver package for Tiger MacIntel that you can download and try out before registering. I have nothing against paying for software if it works, especially when nothing else is available, since what I need is something that just does what it says. My colleague used to be able to connect to our remote mysql dbs from OOo on her previous PPC machine with the PPC binary driver provided by MySQL, and now, just because she has switched to MacIntel, no longer has access to any of our remote mysql dbs via OOo, because the Java X11 bridge implementation is broken or incomplete, or simply because MySQL doesn't supply a binary driver. The point of this rant is this : Actual confirm that their current driver works correctly with OOo 2.0.x, but not with 2.1, so something got broken by the OOo community along the way. It may be a general implementation problem, i.e. not Mac specific, in which case it is up to the guys on the dba-dev list. However, there is a distinct chance that as this is related to a Mac- specific driver, these guys will tell me it's Mac related (as they have done in the past), and the Mac port is not an officially supported port of the OOo project, and that therefore I should go and complain to the Mac developers. So I would basically find myself in a "dog chasing his own tail" situation. And the solution is ? I don't want anyone among the Mac devs to feel aggrieved her, because the work you guys (any women in the group BTW ?) are doing is fantastic and without it there wouldn't even be a Mac port, but there are certain business realities that the Mac project simply does not currently live up to. Actual's drivers work with Excel/Word for Mac, they no longer work with OOo, although they did in the previous branch of development. Simple as that. So do I switch back to Word/Excel just for my lone Mac user, after having grudgingly convinced her to use OOo for the last 3 years, or do I say to hell with it and swap the MacIntel for a PC (and far fewer headaches) ? I'm a business man, not an idealist. It must work, if it doesn't, I'll bin it and switch to something else that does. This might seem harsh, but that's how it is. I have yet to try NeoOffice, because previously this was even more bloatware than OOo, notwithstanding the network printing problems that it also had. Everyone, I apologise in advance for ranting, but I'm desperate for a solution, and I see none forthcoming for as long as the Mac port project remains in its current configuration. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
