wingpeople
Programmer
I've posted this on the ASP forum also, but haven't gotten any suggestions there, so....
I have several ASP pages which work fine when I run them on my local IIS for testing. When I move them to the "real" IIS server, 2 still work, but 1 keeps giving me "unspecified error" messages -- and the line # keeps shifting!
The pages which work simply display info from an Access 97 database. The page which doesn't work has a form for users to fill out to add records to that same Access MDB. I use identical connection strings to look at recordsets in all these pages.
Although the error messages shift to different lines in the script, it seems that the errors always occur in a line such as the 2nd one here:
set rsAudience = Server.CreateObject("ADODB.Recordset"
rsAudience.ActiveConnection = MM_connCMCEventCalendar_STRING
I've tried tossing in Response.Write, Response.End to see how far I get into the script. Oddly, one error on opening a recordset went away after I did this. But, the error "moved" to a different recordset (same connect string).
What do you think is going on? Is the "real" IIS at my client's site configured differently than the "test" IIS on my computer? Why can I work with recordsets from the same MDB in 2 scripts, but not in the 3rd?
I have several ASP pages which work fine when I run them on my local IIS for testing. When I move them to the "real" IIS server, 2 still work, but 1 keeps giving me "unspecified error" messages -- and the line # keeps shifting!
The pages which work simply display info from an Access 97 database. The page which doesn't work has a form for users to fill out to add records to that same Access MDB. I use identical connection strings to look at recordsets in all these pages.
Although the error messages shift to different lines in the script, it seems that the errors always occur in a line such as the 2nd one here:
set rsAudience = Server.CreateObject("ADODB.Recordset"
rsAudience.ActiveConnection = MM_connCMCEventCalendar_STRING
I've tried tossing in Response.Write, Response.End to see how far I get into the script. Oddly, one error on opening a recordset went away after I did this. But, the error "moved" to a different recordset (same connect string).
What do you think is going on? Is the "real" IIS at my client's site configured differently than the "test" IIS on my computer? Why can I work with recordsets from the same MDB in 2 scripts, but not in the 3rd?