This is a discussion on SQL Server and Clipper/dBase within the SQL Server forums, part of the Microsoft SQL Server category; --> I would like to see a Clipper/dbase DBF file as a table in SQL Server 7.0. How can I ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| |||
| "level8" <level8@freemail.hu> wrote in message news:5831dbac.0409010220.56750a9e@posting.google.c om... >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? You can set up a linked server using either OLE DB or ODBC (using the OLE DB provider for ODBC) - see "Configuring Linked Servers" in Books Online. Simon |
| |||
| "Simon Hayes" <sql@hayes.ch> wrote in message news:<4135f11e$1_2@news.bluewin.ch>... > "level8" <level8@freemail.hu> wrote in message > news:5831dbac.0409010220.56750a9e@posting.google.c om... > >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? > > You can set up a linked server using either OLE DB or ODBC (using the OLE DB > provider for ODBC) - see "Configuring Linked Servers" in Books Online. > > Simon 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ó |
| |||
| level8 (level8@freemail.hu) writes: > 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? 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.likvid.likvid? -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinf...2000/books.asp |
| |||
| Erland Sommarskog <esquel@sommarskog.se> wrote in message news:<Xns9558EEF9C1400Yazorman@127.0.0.1>... > level8 (level8@freemail.hu) writes: > > 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? > > 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.likvid.likvid? 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ó |
| |||
| level8 (level8@freemail.hu) writes: > Erland Sommarskog <esquel@sommarskog.se> wrote in message news:<Xns9558EEF9C1400Yazorman@127.0.0.1>... >> 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.likvid.likvid? > > 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. 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@sommarskog.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinf...2000/books.asp |
| |||
| Erland Sommarskog <esquel@sommarskog.se> wrote in message news:<Xns95595FD7F4B81Yazorman@127.0.0.1>... > level8 (level8@freemail.hu) writes: > > Erland Sommarskog <esquel@sommarskog.se> wrote in message > news:<Xns9558EEF9C1400Yazorman@127.0.0.1>... > >> 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.likvid.likvid? > > > > 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. > > 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? 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. |
| |||
| level8 (level8@freemail.hu) writes: > 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. 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= -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinf...2000/books.asp |
| |||
| Erland Sommarskog <esquel@sommarskog.se> wrote in message news:<Xns955CEEE41F54CYazorman@127.0.0.1>... > level8 (level8@freemail.hu) writes: > > 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. > > 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= Thanks. Your suggestion was almost good. The solution is ll.[d:\temp]..likvid. |
| ||||
| level8 (level8@freemail.hu) writes: > Your suggestion was almost good. > The solution is ll.[d:\temp]..likvid. Great to hear that you got it working! -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinf...2000/books.asp |