|
|||||||||
|
|||||||||
|
|||||||||
 |
|||||||||
| |
||
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
|
|||||||||
| |
||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
ASP Free Forums Sponsor:
|
|
Generate data entry and reporting .NET Web apps in minutes, straight from your database. Read our FREE whitepaper “Build Web 2.0 Applications Without Hand-Coding” Download now! |
|
#1
June 6th, 2005, 02:44 AM
|
||||
|
||||
Things You Should Know
I just stumbled upon very essential information that I didn't know before, or at least wasn't sure it's true. that information can solve numerous problems, thus i'll post it here. if you see such information, feel free to post it here as well.
and now to the point: --- ASP Pages, Session State and the Parent Path options are disabled by default in Windows 2003 Server. If do not enable this functionality after installing IIS, IIS returns a 404 error. You can enable these features through the IIS Manager. To enable these options:
--- the above solve 3 very common problems: 1. ASP "is not working" 2. SSI "not working" 3. Session variables "are not working" or blank. Happy Coding! Next Part: http://forums.aspfree.com/showpost....76&postcount=12 Last edited by Shadow Wizard : June 27th, 2006 at 12:44 PM. Reason: added PDF
|
|
#3
June 6th, 2005, 02:57 AM
|
||||
|
||||
|
probably this is available in tutorials as well, but not very visible and known - hopefully being sticky here would make this knowledge more public.
|
|
#4
June 6th, 2005, 03:30 AM
|
||||
|
||||
|
Quote:
Please don't tag on posts. Please create your own thread. Lot's of people will see your question. Thank you. Shadow: Great info. Thanks.
__________________
- Post your code - Post your errors - Be clear - Be courteous PLEASE...Finalise your thread with a solution or confirmation that the last advice worked or failed (We are here to help each other). 
|
|
#5
June 6th, 2005, 03:31 AM
|
||||
|
||||
|
no, I don't have. the above information is not relevant for this... post it as new thread if you didn't post already and I'll try to help in there.
|
|
#6
June 6th, 2005, 03:32 AM
|
||||
|
||||
|
don't worry guys, I'll run cleanup routine on this thread if needed.
|
|
#7
June 6th, 2005, 03:44 AM
|
||||
|
||||
|
seems like we all posted at the same time
no you thread is dirty
__________________
Look! Its a ShemZilla   
|
|
#8
June 8th, 2005, 04:12 PM
|
|||
|
|||
|
hi,
i had your post printed and right in front of my eyes while i was helping him and he was really happy to get it working in end Thank you shadow once again shalom shalom Sammy
|
|
#9
June 8th, 2005, 04:49 PM
|
||||
|
||||
|
Quote:
helping him? who? when? anyway no problem, glad I was of help.
|
|
#10
June 8th, 2005, 04:54 PM
|
||||
|
||||
|
Things You Should Know, Part #2
When using Stored Procedures, or complex SQL code, always have SET NOCOUNT ON in the sql code. When executing such Stored Procedure or SQL Code the result is not normal recordset, but rather set of recordsets. thus, you have to call NextRecordset of the original recordset: Code:
Set rsTemp=objCommand.Execute Set rs=rsTemp.NextRecordset this is usually ignored thus causing errors because the original recordset is Closed. Next Part Last edited by Shadow Wizard : June 23rd, 2005 at 03:45 AM.
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
