Hi Derek, > -----Original Message----- > From: Derek Hinchliffe [mailto:[EMAIL PROTECTED] > Sent: Montag, 8. M�rz 2004 01:59 > To: [EMAIL PROTECTED] > Subject: Re: MS Access and ODBC 7.5.00.10 fails with more > than 100 rows > > > I think I have tracked this problem down a bit further and it > may have > something to do with Access and deciding what is the maximum > number of > rows a query will produce. > > I've read in a number of places that when dealing with linked ODBC > tables in Access you can specify config options by creating an > 'MSysConf' table on the remote database and giving it some > values (and > there is one about results that defaults to 100 apparently). > > If I do an ODBC trace I can see that Access is indeed issuing > a 'SELECT > Config,nValue FROM MSysConf' before it tries to access any linked > tables, so I created an MSysConf table under the user I am using to > connect to the ODBC tables with. But it still produces 'table not > found', I think because there are no quotes around the column > and table > names.
If there are no quotes on the SQL statement, the kernel regards the identifiers as they would have been written with capital letters. So, having a table MSYSCONF with columns CONFIG and NVALUE, the configuration of Access may work. However, the ODBC standard defines accurately how to deal with quote-characters, whether non quoted identifiers are case sensitive etc. Apparantly Access does not evaluate this information for generating the select command for the config-table. HTH Thomas ---------------------------------------------- Dr. Thomas K�tter SAP DB, SAP Labs Berlin Do you know SAP^H^H^H MaxDB ? www.sapdb.org -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
