Hi Derek The MSysConf table schema and use is pretty well explained in the on-line help of Access (at least A97). Did you look that up?
It seems like you are on the right track but you are probably not using the right config entry ... /gustav > Date: 2004-03-08 01:58 > 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 I issue 'SELECT "Config","nValue" FROM "MSysConf"' it works fine, but > I don't think there is a way to change how Access makes the call, so is > there any way I can get the MaxDB ODBC to respond to SELECT > Config,nValue FROM MSysConf properly or am I barking up the wrong tree? > Cheers > Derek >> I am currently connecting to a MaxDB 7.5.00 with ODBC driver >> 7.5.00.10, and trying to get MS Access to work with the tables. >> >> I am able to link the tables fine, and can open them and manipulate >> the data fine. >> >> But if I create any queries (even as simple as SELECT * FROM whatever) >> that result in more than 100 entries, Access reports "ODBC call failed". >> >> If I look in the trace, I get >> --------- >> MASS STATEMENT : FETCH "SQL_CURSOR_0287" >> EXECUTE: CMD : PARSEID: INPUT : 000003E5 00001B01 2A002B00 01000000 >> SQLCODE: 100 ROW NOT FOUND >> START : DATE : 2004-03-05 TIME : 0010:42:39 >> END : DATE : 2004-03-05 TIME : 0010:42:39 >> --------- >> >> In particular I was testing with a SELECT * on a table with 100 >> records, and it worked.. If I add another record it fails. >> >> Any ideas? Is this an MS Access problem or a MaxDB ODBC problem? -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
