Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

On 11/01/2012 11:14 PM, Girvin R. Herr wrote:
Are you starting mysqld with "--skip-networking"?
If so, then remove it for "localhost" access. LO Base uses localhost to access mysqld and will give a failed to connect error if it can't connect via localhost. MyAdmin does not use localhost to connect, so it would work fine while Base will not.

No Gavin I am not!! MySQL starts automatically at Boot.

Dan wrote:
I see you created a user name 'lanw' in My Admin. That is a good start. You also have to use My Admin to define what schema 'lanw' can access. Then you need to define what privileges 'lanw' should have for the databases in those schema.

Thanks Dan
I started MyAdmin and found that the user 'Ianw' was no longer there - so I gave 'Any User' full privileges. This made no difference to my problem.

So then I went back to MyAdmin and created a New User 'Ianw' and give him full privileges and selected all Schemas.

Back to Base - still get 'Communications Failure'. Tried again this time selecting 'Password Needed' and this time it asked me for my Password but after that came back with the 'Communications Failure'

Any more ideas (I don't have much hair left!!!)

Pretoria RSA.


For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.