Hi Ian,
> Hi Alex -
Axel ;)
> I know about all the details you gave me - I was
> trying a UDL file before I mailed the group, and used the DSN
> entry created by the installation (MAXDB) to create a system DSN also.
>
> But no connection - constantly rejected with "-4008 Unkown
> username/password combination". Have tried lot of different
> combinations of DSN and connection strings, but always
> through the "Microsoft OLEDB provider for ODBC Drivers".
> I even tried adding a new user (webuser/webuser) and
> connecting as this one, but no luck there either.
>
> I realise that it is trying to validate with the instance
> because if I change the server name it gives an error
> regarding not locating an instance - therefore I have got so
> far...but not all the way!
Good news. So the problem is unlikely to lie in your os, your
odbc-setup or the dsn-part of your odbc connection string.
> By the way - for further information - I cannot use DB
> manager as the system administrator, and I cannot use SQL
> Studio as database manager operator, but they connect fine
> vice versa. Is this by design? (I cannot use either as
> webuser that I created above - even though I gave him all
> rights, I cannot seem to do anything with him!)
Yes, this is by design, more on this later.
> Could this be a problem with ODBC or my local accounts in general?
Hm. I do not think that your problem lies in the connection string,
you sound pretty able to create a nice one.
Maybe the Max DB User Concept is generating all the confusion
(it sure is a little tricky).
Contrary to other popular databases, you _cannot_ open a
sql session as Database Manager ("dbm" in the default setup).
Only the Database Administrator ("dba"), and the users he created
_within a sql session_ can do this.
Please note: The DBM GUI does not have a sql session. All users
you create there are Database Managers. You can only create a
SQL user with SQL Studio, sqlcli and with dbmcli in sql mode
(although you should not use dbmcli).
DBO is for managing the instance as a whole. Backups, parameters, ...
DBA is for managing tables, users, ....
(although DBA can also create backups, hehe)
Maybe you want to try again with a new db instance with the
default dbm and dba users. Just a little one, to make sure that
the names didn't get confused, and then connect via odbc using
the dba user?
regards, Axel
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
