>>>>> "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> 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.