Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error: The named index does not exist (#238)

Status
Not open for further replies.

Leithal

Programmer
Nov 21, 2001
2
NZ
Hi

I'm new to all this Pervasive SQL and BTrieve stuff, coming from a microsoft background, we are trying to link some tables from a product called Lantis which uses BTrieve databases.

I have installed Pervasive SQL V 7, install service packs 5 and 6 (Client) and I still get the following error when attempting the link:

[Pervasive Software][ODBC Interface][Pervasive Software SQL Engine]The named index does not exist (#238)

Prior to this error message I get a generic ODBC call failed error returned from the ODBC driver manager.

This only happens on some tables, not all.

I'm lost as to where to turn to for answers as the online help gives nothing away in terms of trying to remedy this error.

Any thoughts, suggestion most greatful.

TIA
Leith
 
How are you performing this link? Are the files you are talking about pretty big? Bigger than the ones that do work?

If you are accessing the files via ADO then be sure to use the server side cursor.

If it is the initial connect that is causing you problems then you could look at this which we use to connect via a DSN (the source bit of the string)

strBMConnect = "Provider=MSDASQL.1;Persist Security Info=False;Data Source=" & "CORPORATE"

If you're talking about joining two tables in a query, in version 7 (but not 2000i apparently) you can use (+) to do a left outer join

SELECT * FROM FILEA, FILEB WHERE FILEA.KEY = FILEB.KEY (+)
 
Hi Tom

Thanks for your reply.

I forgot to mention that we are using MS Access 97 and Linked Tables via the Linked Table Manager.

However we have found that by using DAO and QueryDefs we are able to create a DSN-less connection and iterate all records. So thats what we are going to do, dump all the required data into local tables.

BTW: your point re table size might be right as those tables that we had problems with were large tables.

Regards
Leith
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top