Welcome to WebmasterWorld Guest from 22.214.171.124 , register , free tools , login , search , pro membership , help , library , announcements , recent posts , open posts Become a Pro Member
ADODB.Field error '80020009' client gets this message, I see the page fine htdawg
Hi, I have a weird problem, my client cant see a page on his website and gets this message when he tries to open a page now on my computer I can see the page just fine. from what I understand this error means that the record 9in this case a product that is listed on his site does not exist) could this be browser related problem? he tried i.e & firefox. There were no records found. Try another search... ADODB.Field error '80020009' Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record. /sailingdetails.asp, line 0
Could he be looking at a product that no longer exists or is not active, and you are looking at one that exists? For example, he tries: ../sailingdetails.asp?ID=123 (123 does not exist) you try: ../sailingdetails.asp?ID=234 (234 exists) If you are looking at the same page, then that is weird. I cannot see a caching issue causing that. htdawg
the page /sailingdetails.asp?ID=123 opens for me just fine I can see the product but on his computer he cant, he just gets the error code. defanjos
You are accessing the page via the web, and not locally in your computer, correct? To be absolutely sure you are both looking at the same page, email the link to him and yourself, you click on it, and he clicks on it - do you still have the same problem? Just for the heck of it, I would ask him to delete his browser cache. htdawg
I can seethe page online, so I'll tell hime to clear his browser cache and see what happens, i think he might have a problem with his pc/browser. i tried opening the page on to computers and it was ok. bmcgee
It is a server side error, so the problem is not "on his machine" per se. It could be a caching issue that has "gone away" now, but the root of the problem is that your code is not properly handling the situation of the query returning no results. You need to fix that before you start worrying about his cache.