List:MySQL ODBC« Previous MessageNext Message »
From:Stephen Dahl Date:July 15 1999 4:23pm
Subject:RE: Access 2000 vs. Access'97 with MyODBC
View as plain text  
Hello,
I have the same experience with Access 2000.
Basically, what I have tried to do is export a table out of Access 2000 to
MYSQL, and get the same errors as Colin. The same export table works fine in
Access 97 though. Any help is appreciated!

--Steve

> -----Original Message-----
> From: Colin McKinnon [mailto:colin@stripped]
> Sent: Thursday, July 15, 1999 11:16 AM
> To: myodbc@stripped
> Subject: Re: Access 2000 vs. Access'97 with MyODBC
>
>
> At 09:53 15/07/99 -0500, Daniel D. Reid wrote:
> >Greetings,
> >
> >I am trying to set up a MySQL database that will accept online job
> >applications via the web and then allow our HR department to
> view these apps
> >on their desktops via Access over a MyODBC link.  I have been able to
> >accomplish this with Access'97 but I am having great difficulty
> in getting
> >it to work under Access 2000 which my company is moving towards.
>  Are there
> >different config options for 2000 vs. '97?
> >
> >As an example, I tried to export an identical native Access database from
> >both versions.  The '97 ver worked where the 2000 ver failed.  I got the
> >following error from Access 2000:
> >
> >	ODBC-call failed.
> >	[Microsoft][ODBC Driver Manager]Information type out of range (#0)
> >
> >After going through the MySQL log on our server (RedHat 5.2), I
> can see the
> >'97 queries that create the table and then fills it via multiple
> INSERT INTO
> >queries.  The 2000 create query however is malformed.  It has the 'CREATE
> >TABLE' syntax but no table name to create.  It also has after
> that the list
> >of field types but no names.
> <snip>
> Hi Daniel,
>
> Sorry if I haven't understood the issue but .....
>
> Regarding the specific problem you cited - I presume that you
> have attached
> tables in a database and are trying to import the 97 version into the 2000
> version, while the data remains on the MySQL server? Version compatibility
> for more esoteric functions has often been a bit dodgy with MS. Have you
> looked at the definitions and properties of the attached tables
> once you've
> imported them? I'd suggest that you import the database, delete any
> attached tables then reattach them in Access 2000.
>
> HTH
>
> Colin
>
>
> ---------------------------------------------------------------------
> Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
> posting. To request this thread, e-mail myodbc-thread431@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.
>
>

Thread
Access 2000 vs. Access'97 with MyODBCDaniel D. Reid15 Jul
  • Re: Access 2000 vs. Access'97 with MyODBCColin McKinnon15 Jul
    • RE: Access 2000 vs. Access'97 with MyODBCStephen Dahl15 Jul
      • RE: Access 2000 vs. Access'97 with MyODBCDan15 Jul
        • RE: Access 2000 vs. Access'97 with MyODBCJakub Linowski15 Jul
          • RE: Access 2000 vs. Access'97 with MyODBCDan17 Jul
    • RE: Access 2000 vs. Access'97 with MyODBCDaniel D. Reid15 Jul
      • RE: Access 2000 vs. Access'97 with MyODBCJakub Linowski15 Jul
  • Access 2000 vs. Access'97 with MyODBCMichael Widenius30 Jul
    • RE: Access 2000 vs. Access'97 with MyODBCDaniel D. Reid31 Jul
RE: Access 2000 vs. Access'97 with MyODBCDaniel D. Reid15 Jul
  • Re: Access 2000 vs. Access'97 with MyODBCPatrick Sherrill15 Jul
    • RE: Access 2000 vs. Access'97 with MyODBCDaniel D. Reid15 Jul
      • RE: Access 2000 vs. Access'97 with MyODBCPaul DuBois17 Jul