16,011,949 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Member 10272815 (Top 11 by date)
Member 10272815
11-Jun-14 12:26pm
View
Sounds like your asp:Button is the problem then - they're submit buttons and when clicked post the page back to the server. You need to cancel the form submission by either returning false or the result of $("#dialog").dialog (assuming it returns a true/false) from your click function.
Member 10272815
11-Jun-14 9:44am
View
That will result in the count being up to three times greater than expected. For every row that at least one column matches the keyword it will count any of the three columns that are not NULL, not just the ones that match.
Member 10272815
11-Jun-14 9:39am
View
Count(*) is actually faster than count(Column_Name), because SQL will just get a row count for the first, while the second it has to verify that Column_Name is not null before counting the row. So if you're already removing NULLs by your where clause, count(*) is the way to go.
Have you tried breaking your query up in to smaller pieces and seeing where the slow down is?
Try executing
select @totalCount=count(*) from TableName where (Column1 Like '%[YourTestKeywordHere]%')
select @totalCount=count(*) from TableName where (Column2 Like '%[YourTestKeywordHere]%')
select @totalCount=count(*) from TableName where (Column3 Like '%[YourTestKeywordHere]%')
individually and seeing how long they take.
Member 10272815
4-Jun-14 10:22am
View
That only covers one of three potential overlaps. New start time can fall inside an existing appointment, new end time can fall inside an existing appointment, or the new appointment can entirely encompass an existing appointment.
If new start time is before existing end time, and new end time is after existing start time then you should find all conflicts.
Member 10272815
28-May-14 12:54pm
View
How (and where) are you setting imageSize?
Member 10272815
20-May-14 10:26am
View
Your proc doesn't take a CampaignID parameter, and the ProductID parameter is already defined in your query block. However, looking back at your code you don't return a CampaignID, so your value-of should select FK_Campaign instead of CampaignID.
Does the fdsfas display?
Member 10272815
20-May-14 9:49am
View
I think it's supposed to be something like this (I had to add spaces in the xsl tags to get them to show up, make sure you remove them):
< xsl:template name="ProductInCampaignID">
< xsl:for-each select="/root/Product/ProductInCampaign">
<div class="CampId">
< xsl:value-of select="CampaignID">
</div>
Member 10272815
20-May-14 9:48am
View
Deleted
I think it's supposed to be something like this:
<pre lang="xml"><xsl:template name="ProductInCampaignID">
<xsl:for-each select="/root/Product/ProductInCampaign">
<div class="CampId">
<xsl:value-of select="CampaignID" />
</div>
</xsl:for-each>
</xsl:template></pre>
Member 10272815
20-May-14 9:47am
View
Deleted
I think it's supposed to be something like this:<br>
<br>
<pre>
<xsl:template name="ProductInCampaignID"><br>
<xsl:for-each select="/root/Product/ProductInCampaign"><br>
<div class="CampId"><br>
<xsl:value-of select="CampaignID"><br>
</div><br>
<br>
</pre>
Member 10272815
20-May-14 9:15am
View
It's been almost a year since I've touched Storefront, so I can't remember the specifics of how to do it, but the way you're trying to do it is going through C# extension code, not a stored proc. If I remember correctly, most of the pages have a query section at the top, that's where you'd specify a stored proc.
Member 10272815
14-May-14 10:35am
View
Instead of taking a random value between min and max, it splits the range up and selects a number at random from the sub range. So if your min is 0, max is 10 and you want to select 2 numbers the first number will be a random value between 0 and 4 inclusive, and the second will be between 5 and 9 inclusive.
If you selected 10 numbers between 0 and 10, you'd get an array populated with every value from 0 to 9.
Show More