dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: PowerBuilder
Expertise: Beginner
Mar 13, 1998

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


16 table limitation for a datawindow select stmt

Question:
Is there a work around the SQL server 16 table limitation? Maybe temporary tables, Access, or even denormalization of the database tables? The database is large and very complex that I'm working with, so any ideas would help. I'm tring to remember "PowerBuilder is your friend" but I've hit a wall on this table limitation situation.

Answer:
I have run into this problem in the past and was able to work around the problem by using child datawindows to do some of my joins.

For example if you where developing a sales report and needed to join to the office table to get the name of the office. You could just return the office code in the primary select, then in the report datawindow for the office code place a drop-down datawindow which was a list of all the offices. Then PB would automatically show the office description!

There would be no tab order on the report so the user would not be able to tell the difference and you save a join per code table.

DevX Pro
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date