15,888,521 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 Python 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 saberbladez (Top 4 by date)
saberbladez
18-Jun-13 21:30pm
View
Hi cigwork,
The 'sOutlet' is a "dynamic column" which means that each time a new outlet is opened, there will be a new column. Example: existing outlets are sOutlet1, sOutlet2, sOutlet3. so if there is a new outlet opened, a new column will be created for the outlet, being sOutlet4. hence I am having the issue of mapping my row data to the columns itself
saberbladez
17-Jun-13 22:52pm
View
yea thought of that, but it's causing some performance issue, it's taking 3-4s for 1 query to be done, i am thinking of there is an alternative for this as we will be querying for 30outlets for now, in time to come maybe there will be 50outlets which will be another issue
saberbladez
17-Jun-13 22:52pm
View
Deleted
yea thought of that, but it's causing some performance issue, it's taking 3-4s for 1 query to be done, i am thinking of there is an alternative for this as we will be querying for 30outlets for now, in time to come maybe there will be 50outlets which will be another issue
saberbladez
17-Jun-13 22:39pm
View
Hello I have ammended my question maybe it will be clearer now :)