Advertisement

11.14.2007 at 04:52AM PST, ID: 22959744
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.2

Retain default null value in database field if a parameter in a update sproc is empty

Asked by JEH in MS SQL Server, Active Server Pages (ASP)

Tags:

I am using a stored procedure to update values in a database from an asp page.  

If some of the fields are empty, the default value  is Null -  but if I update and there are blank fields on  the form , then I lose the Null value in the database and it gets replaced with a blank field.  This then alters search pages that require the Null to enable the search to return the correct records.

I have searched for examples of this but have only come up with methods where I check in the asp page before running the update stored procedure - ie

filepath=request("filepath")  
If len(filepath)=0 then
filepath=null  ' this null value is then added into the parameters that pass into the stored procedures
End if

This works, but I use the same stored procedure for a number of pages and would like to avoid having to write this type of statement out for each field on each page.

I know its possible to use DBNull in aspx so that a null value passes in the stored procedure- so perhaps the suggestion would be to update the pages to .net.

thanks for your time

Joy

Start Free Trial
[+][-]11.14.2007 at 05:01AM PST, ID: 20279462

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 14-day free trial to view this Assisted Solution or ask the Experts your question.

 
[+][-]11.14.2007 at 07:31AM PST, ID: 20280690

View this solution now by starting your 14-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: MS SQL Server, Active Server Pages (ASP)
Tags: SQL Server
Sign Up Now!
Solution Provided By: talspaugh27
Participating Experts: 2
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-43 / EE_QW_2_20070628