Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Fields not displayed when using "Set Data Source Location"

Status
Not open for further replies.

marckssg

Programmer
Nov 28, 2000
180
GB
Hi,

I've got a series of reports created in Crystal 9 from a Postgres database. I'm in the process of updating these reports using Crystal XI and a new Postgres database.

When I go to Set Data Source Location everything goes as you'd expect and is straight forward, until I come across a text field. Text fields are not being listed as availble fields, so I'm left with a field I can't match.

If on a sample database I change the data type to varchar 255 it works ok.

Is there anything I can do on the Crystal side to avoid changing the live database?

Cheers

Marc
 
I would think the reverse to be the more likely case, that CR 9 wouldn't show them.

One option that comes to mind is to create Views on the database and CAST/CONVERT them there.

The other would be to use a Add Command and do it in there.

What happens if you go directly against the tables?

And are you turning off the Match Type in the mapping screen? It may be that CR XI sees them as a different type and once you turn this off it will allow you to properly map them.

-k
 
Hi

If I add the table into a new report I can see all the fields no problem and yes I have turned off the match data type.

Might try the add command option, but was rather hoping to find a more generic solution I've got hundreds of these reports to update!

Cheers

Marc
 
Doesn't make any sense to me...

Turning off the match type should be the equivalent of bringing in a new table.

Anyway, the Add Command should work, but it's a tad ugly and you can't use multiple value parameters then.

-k

 
Like I say we've done abit of testing on a test database and changed the data type from "text" which has an unlimted length to varchar 255 and it works fine. But the DBA won't let me use this solution on the life system for his own reasons!

Don't think I'll be able to use the command option either if its going to affect multiple value parameters.

Looks like I'll have to create them all from scratch which means what should have been a few days of a job is going to turn into an epic task!

Agree that it doesn't make any sense! Thanks for the advice,

Cheers

Marc
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top