how to print a datareport with output of 300 fields per record from 3 tables?

[Vinokbhai r k]

I want to print a report using vb6 datareport. The report consists of details of one employee per page. Each employee has various details in 300 fields divided into 3 tables.
With the select command I am not able to fetch more than 192 fields at a time. How to go about it? Please guide me.

[CyberSoftHari]

Point out your database and its version.Can you describe that 300 fields (Basically a report is a short description about a record in a single page).
Are you asking about cross tab query?

[Rabbit]

I honestly don't see how a 300 column report could be usable to a user. That's just information overload. I also suspect that the database design is unnormalized.

[Vinokbhai r k]

The database consists of intime,outtime,working hours, Overtime etc.of all 31 days in a month. This is a landscape report. like:
emp name day1 day2 day3..............................day31
--------------------------------------------------------------
in1 in2 in3 .............................in31
out1 out2 out3.............................out31
work1 work2 ork3............................work31
OT1 OT2 OT3..............................OT31
etc. etc.
I have 31 fields for intime, another 31 fields for outtime and so on.
Pl.guide me.
thanks.

[Vinokbhai r k]

below day1 of that month I am showing the details- that is in1,out1,work1,ot1 etc.
below day2 I am showing the details that is in2, out2,work2,ot2 etc.

[CyberSoftHari]

As Rabit said there is no normalization and just printing entered junk data. How you view this report?
1. Employee wise?
2. Date, or Month wise?
3. Working time wise?
Whatever, you should plan your report (like normalize, grouping fields, merging information etc.,) because showing everything will overload information in a report and this is going to be an homework here.

[Rabbit]

Your data is highly unnormalized. At most you only need 3 fields to display the data you mentioned: Employee ID, Day Number, Work Type. There is absolutely no need for 300 fields and all the complications that come with it.

[Killer42]

Don't know about the rest of you, but I get asked to produce some pretty stupid stuff at work sometimes, and telling the boss "there's no need for that" or "it's not normalised" doesn't cut much ice.

[Rabbit]

I'm assuming the boss is database illiterate. In which case, they only care about the look, and not so much about the database design itself. In those situations, I normalize the database, but display it in the manner the user wants.

[CyberSoftHari]

I told merge information like. in1, in2 to in31 and out1, out2 to out31 as an single text to a report field.