A
Augie Dawg
Over the last 2 years I've developed quite a few ASP pages using the FP 2002
DRW to access and update 5 different database files, mostly .mdb files, with
some .xls files. About 1 month ago, about 3/4 of these database queries
started returning errors instead of data. I immediately surmised it was a
hosting issue, and slogged through a lot of time with my host's tech
support, reinstalling FP extensions, resetting permissions, removing,
reinstalling, and updating FP 2002, all to no avail. After a couple weeks of
telling me my code was faulty (funny, it had worked for the last two years
just fine, and has not been modified), my host finally said their ODBC and
MDAC components were corrupt, and that they reinstalled them with an updated
version, but that now any query with a reference to a table that had a space
in its name would fail. I dutifully changed the few table names and handful
of queries I had against such tables, and things still failed in the same
manner. Ultimately unsatisfied with the responses I was getting from the
host, I finally changed hosts 2 days ago. The DNS got pointed to the new
host's server yesterday, & I used FP to upload the site, only to find I'm
still getting the same errors as on the previous host.
The error messages I'm getting are all over the map, from
"HTTP 500 - Internal server error "
to
"Database Results Error
The operation failed. If this continues, please contact your server
administrator."
to
"
ADODB.Recordset error '800a0cc1'
Item cannot be found in the collection corresponding to the requested name
or ordinal."
(This last message can be generated after correctly returning several
columns of the first row of results.)
The really weird thing about these failures is that other DRW queries
against the same table are working perfectly!!!
I've spent many hours poring over the code that FP generated, both code that
works and code that fails, and it all looks fine to me. I've used the
"compact and repair" function in Access 2002 on the database file, to no
avail.
The one semi-strange thing I noticed is the following entry in the
global.asa file:
<mso:connectionstatus msdt:dt="string">OSSCData_1=1 LibraryData=1 Events=0
Vendors=0 UploadedFiles=1</mso:connectionstatus>
I would think that all values would be the same, since no connection was
open to any of them that I was aware of.
Does anyone have any thoughts on what might be broken? I'm getting
desparate!!!
Thanks in advance,
A.D.
DRW to access and update 5 different database files, mostly .mdb files, with
some .xls files. About 1 month ago, about 3/4 of these database queries
started returning errors instead of data. I immediately surmised it was a
hosting issue, and slogged through a lot of time with my host's tech
support, reinstalling FP extensions, resetting permissions, removing,
reinstalling, and updating FP 2002, all to no avail. After a couple weeks of
telling me my code was faulty (funny, it had worked for the last two years
just fine, and has not been modified), my host finally said their ODBC and
MDAC components were corrupt, and that they reinstalled them with an updated
version, but that now any query with a reference to a table that had a space
in its name would fail. I dutifully changed the few table names and handful
of queries I had against such tables, and things still failed in the same
manner. Ultimately unsatisfied with the responses I was getting from the
host, I finally changed hosts 2 days ago. The DNS got pointed to the new
host's server yesterday, & I used FP to upload the site, only to find I'm
still getting the same errors as on the previous host.
The error messages I'm getting are all over the map, from
"HTTP 500 - Internal server error "
to
"Database Results Error
The operation failed. If this continues, please contact your server
administrator."
to
"
ADODB.Recordset error '800a0cc1'
Item cannot be found in the collection corresponding to the requested name
or ordinal."
(This last message can be generated after correctly returning several
columns of the first row of results.)
The really weird thing about these failures is that other DRW queries
against the same table are working perfectly!!!
I've spent many hours poring over the code that FP generated, both code that
works and code that fails, and it all looks fine to me. I've used the
"compact and repair" function in Access 2002 on the database file, to no
avail.
The one semi-strange thing I noticed is the following entry in the
global.asa file:
<mso:connectionstatus msdt:dt="string">OSSCData_1=1 LibraryData=1 Events=0
Vendors=0 UploadedFiles=1</mso:connectionstatus>
I would think that all values would be the same, since no connection was
open to any of them that I was aware of.
Does anyone have any thoughts on what might be broken? I'm getting
desparate!!!
Thanks in advance,
A.D.