|
| |
|
|
bango
Posts: 40
Joined: 8/23/2004
Status: offline
 |
E_FAIL status - 6/23/2005 13:39:42
Error:
Microsoft Cursor Engine (0x80004005)
Data provider or other service returned an E_FAIL status.
/_fpclass/fpdbrgn1.inc, line 211
I am having this error and pulling my hair trying to figure out why. It seems that once my query gets larger in the backend Access DB, I received this error on my frontend ASP DRW. The FPClass reference is attempting to page correctly and I am wondering if iMaxRecords within the DRW might be messing things up?
Any help please?
|
|
|
|
bango
Posts: 40
Joined: 8/23/2004
Status: offline
|
RE: E_FAIL status - 6/23/2005 18:52:48
Yes, I do have a memo field however I tested transitioning it to a text field and still received the same effect. I have looked at a few articles and see that you suggest using the OLEDB jet 4.0 drivers. I am not sure how to transition my DRW (dieted) code to the OLEDB rather than the DSN?? I am currently using. Could you take a look or point me to a good example ?
<!--#include file="_fpclass/fpdblib.inc"-->
<% if 0 then %>
<SCRIPT Language="JavaScript">
document.write("<div style='background: yellow; color: black;'>The Database Results component on this page is unable to display database content. The page must have a filename ending in '.asp', and the web must be hosted on a server that supports Active Server Pages.</div>");
</SCRIPT>
<% end if %>
<%
fp_sQry="SELECT * FROM qsel_Moto WHERE (Manufacturer Like '%::Manufacturer::%' AND Model Like '%::Model::%' AND BodyStyle Like '%::Style::%' AND VehicleTypeID = '::VTID::' AND (SubdistrictID Like '%::SBID::%') AND (SalePrice >= ::MinSP:: AND SalePrice <= ::MaxSP::) AND YearModelType >= '::MINY::' AND YearModelType <= '::MAXY::' AND LD <= ::LD:: AND Special Like '%::SPC::%' AND DealershipID Like '%::DLID::%' AND NewUsed Like '%::NU::%') ORDER BY ::SortColumn:: ::Sort::"
fp_sDefault="SortColumn=YearModelType"
fp_sNoRecords="<tr><td colspan=7 align=""LEFT"" width=""100%""></td></tr>"
fp_sDataConn="customers"
fp_iMaxRecords=2000
fp_iCommandType=1
fp_iPageSize=15
fp_fTableFormat=True
fp_fMenuFormat=False
fp_sMenuChoice="YearModelType"
fp_sMenuValue="YearModelType"
fp_sColTypes="&Username=202&VehicleTypeID=202&SaleType=202&MarketID=3&Manufacturer=202&Model=202&ID=3&ManModel=202&YearModelType=202&Color=202&Market=202&YearMakeModel=202&Mileage=3&Sale Price=202&BestOffer=202&BodyStyle=202&Engine=202&Transmission=202&Cylinders=202&Vin=202&Stock=202&Description=203&Options=202&City=202&State=202&Email=202&Phone=202&FirstName=202&LastName=202&Seller=202&SellerName=202&SellerNameHeader=202&SellerStreet=202&SellerAddress=202&SellerContactRequest=202&DealershipID=202&Website=202&Zip=202&Subdistrict=202&YearModel=202&SaleDesignation=202&AutoAge=202&Image=202&Doors=202&DealerImage=205&DriveTrain=202&Password=202&DC=135&LD=202&DU=135&DUD=135&DDs=202&YMM=202&SP=202&M=202&VehicleImages=202&LogoImages=202&ContactImages=202&FinanceImages=202&ContactPreference=202&SubdistrictID=202&PTNV=202&SellerLink=202&PhotoUploaded=&SalePrice=&SubdistrictName=&Special=&NewUsed=&"
fp_iDisplayCols=7
fp_fCustomQuery=False
BOTID=0
fp_iRegion=BOTID
%>
<!--#include file="_fpclass/fpdbrgn1.inc"-->
| |
|
|
|
rubyaim
Posts: 757
Joined: 6/22/2005
Status: offline
|
RE: E_FAIL status - 6/26/2005 2:41:36
Bango, I read your post and thought that E_FAIL is an error I'd never seen - but I thought too soon as it appeared for me today when I modified an already very large select query in Access 2000.
I only added an ID field from a table already selected in the query and the E_FAIL was appearing on the records that had that ID (15 out of 2012 only so it was easy to pin point the problem). As a quick fix I amended the query back to what it was. There are no memo fields in the query.
Spooky, I was too scared to muck with the global.asa as I'm not really confident enough yet to tackle connections. Would you have a link to any info about the differences in these connections? Sorry, am not sure what to search for.
It would be handy to have that ID field in this particular query. Am thinking of trying this on my PWS and amending the query to return '0' if there is no ID to display (am not convinced but am curious if it would work - will probably get an E_FAIL on all records instead of just 15).
Sally
_____________________________
Sally
| |
|
|
|
jmlbige
Posts: 62
Joined: 7/22/2004
Status: offline
|
RE: E_FAIL status - 8/23/2005 16:04:42
This error simply is due to a Null value in one of your search criteria fields.
Example
If you have search form to search for people's name by either their first name or last name, and one of the fields is NULL in the database, it will return this error.
FIX
Update the records in your database to contain at least 1 character, or change your search criteria.
Hope this helps.
| |
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
k¥ 