Hi,
I have a puzzling question. i got the error Microsoft VBScript runtime error '800a01a8' - Object required on page 2 but when I click back to the Page1 and then click Submit again, the page works!
what I'm trying to say is that it doesn't work the first time but is able to update on the second try (after I click the back Button and then the Submit buttonin IE).
This is the code on Page 2.
<!--#include file="../Connections/Onlin
<% Dim con, sql_update
sql_update = "Update Pendaftaran Set Nama = '"& Session("NamaValue") &"', NIP = '"& Session("NIPValue") &"' Where PendaftaranID = " & Session("PendaftaranID") & " "
Set con = Server.CreateObject("ADODB
con.Open MM_OnlineRegistration_STRI
con.Execute sql_update
con.Close
Set con = nothing
Response.Redirect ("DaftarPerserta.asp?Kursu
%>
I'm sure it works cos it's able to update on the second try (but not the 1st time)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Basically, when you use option explicit, the system scans the ASP for variables and objects used for and attempts to match them with Dim statements. Once it comes across one it creates an object store for it before executing the code.
Under certain versions of the script engine, dynamically created objects didn't get properly initialised when they got thier Set statement until the page was cached in the ASP memory block. So on occasion you got that error. I learnt this from Microsoft on a specialist IIS course about 6 years ago where we tested different methods of coding in ASP... Had a great example of a piece of bad db access looping thru 100 records that through the cache engine ran about 20% faster than the proper way of doing it due to the way ASP cached stuff. Once it got to 120 records the thing reversed in performance...
Business Accounts
Answer for Membership
by: SimonBlakePosted on 2006-05-31 at 00:58:54ID: 16796448
Can you response.Write the value of the MM_OnlineRegistration_STRI
Also, put an Option Explicit into the page at the top as this forces the runtime to do a few extra checks (But makes the code run slightly aster)
Simon.