SQL Server and Clipper/dBase

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • level8

    SQL Server and Clipper/dBase

    I would like to see a Clipper/dbase DBF file as a table in SQL Server
    7.0. How can I SELECT rows from DBF file? Should I use OLE DB Provider
    or ODBC, and how?
  • Simon Hayes

    #2
    Re: SQL Server and Clipper/dBase


    "level8" <level8@freemai l.hu> wrote in message
    news:5831dbac.0 409010220.56750 a9e@posting.goo gle.com...[color=blue]
    >I would like to see a Clipper/dbase DBF file as a table in SQL Server
    > 7.0. How can I SELECT rows from DBF file? Should I use OLE DB Provider
    > or ODBC, and how?[/color]

    You can set up a linked server using either OLE DB or ODBC (using the OLE DB
    provider for ODBC) - see "Configurin g Linked Servers" in Books Online.

    Simon


    Comment

    • level8

      #3
      Re: SQL Server and Clipper/dBase

      "Simon Hayes" <sql@hayes.ch > wrote in message news:<4135f11e$ 1_2@news.bluewi n.ch>...[color=blue]
      > "level8" <level8@freemai l.hu> wrote in message
      > news:5831dbac.0 409010220.56750 a9e@posting.goo gle.com...[color=green]
      > >I would like to see a Clipper/dbase DBF file as a table in SQL Server
      > > 7.0. How can I SELECT rows from DBF file? Should I use OLE DB Provider
      > > or ODBC, and how?[/color]
      >
      > You can set up a linked server using either OLE DB or ODBC (using the OLE DB
      > provider for ODBC) - see "Configurin g Linked Servers" in Books Online.
      >
      > Simon[/color]

      Hi, Simon,
      I have a d:\temp\likvid. dbf file. I created an ODBC connection named
      "dbase" and after that I created a linked server named LL. In
      Enterprise Manager I can see the LL and the LIKVID table, but that's
      all. When I "select * from ll...likvid" in Query Analizer, then I get
      a message: "Invalid schema or catalog specified for provider
      'MSDASQL'." What is the problem?

      Regard
      László

      Comment

      • Erland Sommarskog

        #4
        Re: SQL Server and Clipper/dBase

        level8 (level8@freemai l.hu) writes:[color=blue]
        > I have a d:\temp\likvid. dbf file. I created an ODBC connection named
        > "dbase" and after that I created a linked server named LL. In
        > Enterprise Manager I can see the LL and the LIKVID table, but that's
        > all. When I "select * from ll...likvid" in Query Analizer, then I get
        > a message: "Invalid schema or catalog specified for provider
        > 'MSDASQL'." What is the problem?[/color]

        What does the Schema and Catalog column say for LIKVID? You probably need
        to supply something between the dots, but not knowing DBASE, I have no
        idea of what. May be ll.likvid.likvi d.likvid?

        --
        Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

        Books Online for SQL Server SP3 at
        Get the flexibility you need to use integrated solutions, apps, and innovations in technology with your data, wherever it lives—in the cloud, on-premises, or at the edge.

        Comment

        • level8

          #5
          Re: SQL Server and Clipper/dBase

          Erland Sommarskog <esquel@sommars kog.se> wrote in message news:<Xns9558EE F9C1400Yazorman @127.0.0.1>...[color=blue]
          > level8 (level8@freemai l.hu) writes:[color=green]
          > > I have a d:\temp\likvid. dbf file. I created an ODBC connection named
          > > "dbase" and after that I created a linked server named LL. In
          > > Enterprise Manager I can see the LL and the LIKVID table, but that's
          > > all. When I "select * from ll...likvid" in Query Analizer, then I get
          > > a message: "Invalid schema or catalog specified for provider
          > > 'MSDASQL'." What is the problem?[/color]
          >
          > What does the Schema and Catalog column say for LIKVID? You probably need
          > to supply something between the dots, but not knowing DBASE, I have no
          > idea of what. May be ll.likvid.likvi d.likvid?[/color]

          Hi, Erland,

          Yes. My problem is same: What does the Schema and Catalog column say
          for a single DBF file? The dBase program isn't important now, it's
          only one data file. I don't know that how the SQL Server can see it
          through the ODBC. When I try the connection name (dbase) or the
          directory (d:\temp) between dots, then the result is same.

          Do you have other idea?

          László

          Comment

          • Erland Sommarskog

            #6
            Re: SQL Server and Clipper/dBase

            level8 (level8@freemai l.hu) writes:[color=blue]
            > Erland Sommarskog <esquel@sommars kog.se> wrote in message[/color]
            news:<Xns9558EE F9C1400Yazorman @127.0.0.1>...[color=blue][color=green]
            >> What does the Schema and Catalog column say for LIKVID? You probably need
            >> to supply something between the dots, but not knowing DBASE, I have no
            >> idea of what. May be ll.likvid.likvi d.likvid?[/color]
            >
            > Yes. My problem is same: What does the Schema and Catalog column say
            > for a single DBF file? The dBase program isn't important now, it's
            > only one data file. I don't know that how the SQL Server can see it
            > through the ODBC. When I try the connection name (dbase) or the
            > directory (d:\temp) between dots, then the result is same.[/color]

            You are right that Schema and Catalog may not very relevant for a DBF
            file, but what I meant was: When you look at the tables in the linked
            server from Enterprise Manager, what values do you see there? Would
            these work?


            --
            Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

            Books Online for SQL Server SP3 at
            Get the flexibility you need to use integrated solutions, apps, and innovations in technology with your data, wherever it lives—in the cloud, on-premises, or at the edge.

            Comment

            • level8

              #7
              Re: SQL Server and Clipper/dBase

              Erland Sommarskog <esquel@sommars kog.se> wrote in message news:<Xns95595F D7F4B81Yazorman @127.0.0.1>...[color=blue]
              > level8 (level8@freemai l.hu) writes:[color=green]
              > > Erland Sommarskog <esquel@sommars kog.se> wrote in message[/color]
              > news:<Xns9558EE F9C1400Yazorman @127.0.0.1>...[color=green][color=darkred]
              > >> What does the Schema and Catalog column say for LIKVID? You probably need
              > >> to supply something between the dots, but not knowing DBASE, I have no
              > >> idea of what. May be ll.likvid.likvi d.likvid?[/color]
              > >
              > > Yes. My problem is same: What does the Schema and Catalog column say
              > > for a single DBF file? The dBase program isn't important now, it's
              > > only one data file. I don't know that how the SQL Server can see it
              > > through the ODBC. When I try the connection name (dbase) or the
              > > directory (d:\temp) between dots, then the result is same.[/color]
              >
              > You are right that Schema and Catalog may not very relevant for a DBF
              > file, but what I meant was: When you look at the tables in the linked
              > server from Enterprise Manager, what values do you see there? Would
              > these work?[/color]

              Nothing. A big nothing. I can see only LIKVID table as an object (or
              icon), but I can not see into the table. I can not open this table in
              Enterprise Manager.

              Comment

              • Erland Sommarskog

                #8
                Re: SQL Server and Clipper/dBase

                level8 (level8@freemai l.hu) writes:[color=blue]
                > Nothing. A big nothing. I can see only LIKVID table as an object (or
                > icon), but I can not see into the table. I can not open this table in
                > Enterprise Manager.[/color]

                I'm afraid that I've run out of suggestions. Well, ll.[ ].[ ].LIKVID
                maybe.

                I did find a thread on a Russian SQL forum where various suggestions
                are tried. My Russian is very rudimentary, but maybe of the suggestions
                there is something you could try.





                --
                Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

                Books Online for SQL Server SP3 at
                Get the flexibility you need to use integrated solutions, apps, and innovations in technology with your data, wherever it lives—in the cloud, on-premises, or at the edge.

                Comment

                • level8

                  #9
                  Re: SQL Server and Clipper/dBase

                  Erland Sommarskog <esquel@sommars kog.se> wrote in message news:<Xns955CEE E41F54CYazorman @127.0.0.1>...[color=blue]
                  > level8 (level8@freemai l.hu) writes:[color=green]
                  > > Nothing. A big nothing. I can see only LIKVID table as an object (or
                  > > icon), but I can not see into the table. I can not open this table in
                  > > Enterprise Manager.[/color]
                  >
                  > I'm afraid that I've run out of suggestions. Well, ll.[ ].[ ].LIKVID
                  > maybe.
                  >
                  > I did find a thread on a Russian SQL forum where various suggestions
                  > are tried. My Russian is very rudimentary, but maybe of the suggestions
                  > there is something you could try.
                  > http://www.sql.ru/forum/actualthread...&tid=14519&hl=[/color]

                  Thanks.
                  Your suggestion was almost good.
                  The solution is ll.[d:\temp]..likvid.

                  Comment

                  • Erland Sommarskog

                    #10
                    Re: SQL Server and Clipper/dBase

                    level8 (level8@freemai l.hu) writes:[color=blue]
                    > Your suggestion was almost good.
                    > The solution is ll.[d:\temp]..likvid.[/color]

                    Great to hear that you got it working!



                    --
                    Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

                    Books Online for SQL Server SP3 at
                    Get the flexibility you need to use integrated solutions, apps, and innovations in technology with your data, wherever it lives—in the cloud, on-premises, or at the edge.

                    Comment

                    • Ellen K.

                      #11
                      Re: SQL Server and Clipper/dBase

                      Our legacy apps are Clipper/dBase and we discovered that trying to
                      link to the Advantage Database Server to talk to them was Not A Good
                      Thing.

                      If you set up your dbf "database" as an ODBC data source, you can use
                      DTS to import a table or the result of a simple query into a SQL
                      Server table, where you can work with it. NOTE: Do NOT try to use
                      OLE DB against it, this blows up DTS.

                      On 2 Sep 2004 01:52:24 -0700, level8@freemail .hu (level8) wrote:
                      [color=blue]
                      >"Simon Hayes" <sql@hayes.ch > wrote in message news:<4135f11e$ 1_2@news.bluewi n.ch>...[color=green]
                      >> "level8" <level8@freemai l.hu> wrote in message
                      >> news:5831dbac.0 409010220.56750 a9e@posting.goo gle.com...[color=darkred]
                      >> >I would like to see a Clipper/dbase DBF file as a table in SQL Server
                      >> > 7.0. How can I SELECT rows from DBF file? Should I use OLE DB Provider
                      >> > or ODBC, and how?[/color]
                      >>
                      >> You can set up a linked server using either OLE DB or ODBC (using the OLE DB
                      >> provider for ODBC) - see "Configurin g Linked Servers" in Books Online.
                      >>
                      >> Simon[/color]
                      >
                      >Hi, Simon,
                      >I have a d:\temp\likvid. dbf file. I created an ODBC connection named
                      >"dbase" and after that I created a linked server named LL. In
                      >Enterprise Manager I can see the LL and the LIKVID table, but that's
                      >all. When I "select * from ll...likvid" in Query Analizer, then I get
                      >a message: "Invalid schema or catalog specified for provider
                      >'MSDASQL'." What is the problem?
                      >
                      >Regard
                      >László[/color]

                      Comment

                      Working...