Problem with 6.03 pipeline?

rbuser

I've just spent about two hours unsuccessfully trying to figure out why my
dbpipeline won't display persistent fields from a tquery.
The only thing I can figure is that there's a problem with RB (6.03).

The problem is that no matter how many times I've tried it, my dbpipline
only allows the fields through "email" to show up in the report designer,
and I can't get "fullname", or "citystatezip" to display at all.

I'm trying to output mailing labels so I need the contatentated fields.

Any ideas?

Here's the sql:

select First_Name FirstName, Last_Name LastName, address_1 Address1,
address_2 Address2, City, State, Zip, email_address email,
first_name fullname, city+', '+state+' '+zip citystatezip
from student s join address a ON s.student_id = a.person_id
and s.address_type = a.address_type

--
Mike

digitalmetaphors

Check the fields that are defined onthe datapipeline by double clicking on
the datapipeline. At Delphi design time, sometimes new fields don't get
autocreated after the pipeline has created the fields for the first time.
Try toggling the Pipeline.AutocreateFields property in the object inspector
to get it to refresh. If it still cannot create the field objects, you can
delete the date pipeline and drop a new one on the form. It should create
the fields when you connect the pipeline.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Jim,

That's why I'm coming here!

Here's what I've tried so far:

1. Reinstall Delphi (including RB Ent 6.03)
2. Reinstall Windows 98 SE
3. Remove all RB components from form, save form, close Delphi, reopen all,
drop new pipeline & set data source, drop new report, select "new" and
specify labels.
4. Toggle True/False on AutocreateFields (many times)

The fields mentioned STILL don't show up!

Any more ideas I can try?

Mike

rbuser

One clue to the problem might be that I originally cut and pasted a
pipeline and report on this form and it caused all kinds of Win API
problems. I had to end up removing the components.

Is it possible that my new pipeline is somehow thinking that it's hooking
back to the original data (which didn't contain those new fields)?

I've edited the DFM but can't see anything of significance in there. Maybe
I'm looking for the right thing?

Mike

rbuser

Well, after all that, it was a corrupted datasource component that was
causing the problem.
After I deleted and replaced it, everything worked fine.

First time I've seen that one (and hopefully the last)...

Mike

rbuser

I am glad you found it, but I would have done that before reinstalling
Windows