From: Pat Sherrill
Date: February 7 2000 11:03am
Subject: Re: Access97 to access multiple databases from same MySQL servervia ODBC
List-Archive: http://lists.mysql.com/myodbc/1185
Message-Id: <00e801bf715a$f9a070e0$1e0110ac@pms98>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I'm sorry, I jumped in the middle of this thread without seeing the previous
email.  If I understand what's going on here, you have attempted to create a
single DSN for multiple databases.  The Access MyODBC combination will allow
for multiple tables to one DSN, but not multiple databases with one DSN.
You would need make a DSN for each database.  I'm not aware of any way of
changing databases within a linked DSN by way of the Access interface.  This
could of course be accomplished with the native interface or with hand
coding using MSVC or similar and sending SqlDirect calls to the driver (not
for the uninitiated, however).

Someone on the list with more Access expertise may have a solution, but with
my level of expertise what you are trying to do with the Access interface is
not within reach.

Sorry I couldn't be of more help.

Pat...
patrick@stripped

----- Original Message -----
From: Michael Widenius <monty@stripped>
To: Federico Sevilla III <jijo@stripped>
Cc: MyODBC Mailing List <myodbc@stripped>
Sent: Saturday, February 05, 2000 10:00 AM
Subject: Re: Access97 to access multiple databases from same MySQL servervia
ODBC


> >>>>> "Federico" == Federico Sevilla <jijo@stripped> writes:
>
> Federico> Hi! :-)
> Federico> On Tue, 1 Feb 2000 at 15:52, Michael Widenius wrote:
> >> The above should work. Which MySQL version are you using?  Are you sure
> >> that the test_oc exists in the contactmgr database?
>
> Federico> I'm using MySQL v3.22.27 (yes, I'm working on upgrading it to
3.22.30
> Federico> already) on a Linux kernel 2.2.14 machine. MyODBC is 2.50.29.00
on a
> Federico> Windows 95 4.00.950B machine.
>
> Federico> The options used in the connect screen: allow BIG results,
> Federico> safety. Everything else is unchecked. Basically this is what
happens:
>
> Federico> DATABASE dbase_test_01
> Federico> TABLE dbase_test_01.table01
>
> Federico> DATABASE dbase_test_02
> Federico> TABLE dbase_test_02.table02
>
> Federico> Sequence of actions:
> Federico> 1. Link both tables using machine DSN name "MySQL".
> Federico> 2. Exit Access.
> Federico> 3. Open Access database.
> Federico> 4. Open link to dbase_test_01.table01, login, all is okay.
> Federico> 5. Open link to dbase_test_02.table02, error because it is
trying to
> Federico> open dbase_test_01.table02 which of course does NOT exist.
>
> Federico> Alternate sequence:
> Federico> ...
> Federico> 4. Open link to dbase_test_02.table02, login, all is okay.
> Federico> 5. Open link to dbase_test_01.table01, error because it is
trying to open
> Federico> dbase_test_02.table01 which again, does not exist.
>
> Federico> I've worked around this problem by having multiple machine DSNs
with
> Federico> different names. But of course things would be nicer if I could
share one
> Federico> DSN. Hmm ... any other thoughts? Please help. Thanks. :)
>
> The big problem here is that I don't use Access, so I don't know what
> happens behind the scenes.
>
> Have you tried to make a ODBC and a MyODBC trace file to get some
> notion about what happens?  It looks like Access doesn't supply
> MyODBC with the database name when it opens the tables, but it's funny
> that it works when you link the tables.
>
> Regards,
> Monty
>
> ---------------------------------------------------------------------
> Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
> posting. To request this thread, e-mail myodbc-thread1183@stripped
>
> To unsubscribe, send a message to the address shown in the
> List-Unsubscribe header of this message. If you cannot see it,
> e-mail myodbc-unsubscribe@stripped instead.
>
>