>>The following code works without a problem:
>>

>>< %
>>Set oConn = Server.CreateObject("ADODB.Connection")
>>ConnStr = "Driver=Microsoft Visual Foxpro Driver; UID=userID;SourceType=DBC;SourceDB=c:\inetpub\wwwroot\tip\login\data\tipdatabase.dbc"
>>oConn.Open ConnStr
>>
>>sql = "select * from rta_basedata where tip_id = " & lcTIP_id
>>Set oRTA_Basedata = oConn.Execute(sql)
>>% >
>>

>>The following code produces an error
>>

>>< %
>>sql = "select * from rta_payments where tip_id = " & lcTIP_id
>>Set oRTA_Payments = oConn.Execute(sql)
>>% >
>>
>>Error Type:
>>Microsoft OLE DB Provider for ODBC Drivers (0x80040E37)
>>[Microsoft][ODBC Visual FoxPro Driver]Not a table.
>>/tip/rtapage5.asp, line 41
>>

>>
>>Both tables are located in the same folder and belong to the same database. The forward and back links seem to be in order inboth directions. Any ideas as to what's causing this problem?
>
>Maybe it is a table that ODBC driver can't handle. Why do you use OLEDB for ODBC driver and not directly VFPOLEDB driver?
>Cetin
Thanks Cetin -
The answer to your question is "because I'm not educated enough to know there are choices and what the difference might be." Are you suggesting a different connection string?