When I connect using ODBC in Windows, all is well. Using ODBC for the
Novell provider works OK unless there is a "Fat Client" which
connected to the database first, in which case the Active Server Pages
application hangs.
When I connect using OLE-DB, the application connects and some pages
work. However, all the search screens fail with:
HTTP 500.100 - Internal Server Error - ASP error
Error type:
ADODB.Recordset(0x800A0CB3)
Object or provider is not capable of performing requested operation
Page:
POST 103 bytes to /mstar/ReviewWO.asp
Some search screens use dates, some do not. But, they all have one
thing in common: they use the "Page x of y" functionality of ADO.
Questions:
1) Does the Novell ASA7 have an OLE-DB Provider?
2) Is Page x of y supported in the ASA7 OLE-DB provider? Or, do I
need to upgrade?
Thank you.
VictorReinhart
This problem was solved. The ASP application tried to create an
index, which requires a full table lock. The table lock could not be
acquired since there was an open cursor in the Fat Client, doing a
PowerBuilder DataWindow Retrieval using 'RetrieveAsNeeded'.
Oracle and SQL Server are OK as they find the index already exists and
don't try to acquire the table lock.
> 1) Does the Novell ASA7 have an OLE-DB Provider?
Still, I don't know. But, the ODBC interface does work now.
> 2) Is Page x of y supported in the ASA7 OLE-DB provider? Or, do I
> need to upgrade?
After upgrading to SQL Anywhere 7.0.3, this problem went away.
VictorReinhart