Can't format embedded fields anymore

[Former Member]

For some reason, I can no longer change the format of a field which I have embedded in a text object.

When I right-click the embedded field, the option to do so is greyed out, and this happens regardless of which report I open, or if I create a new one.

I am using CR 12.1.0.892 on Vista Ultimate x32.

[qadeer_akhtar]

Here is how I solved my issue;

[Former Member]

I am also having the problem with formatting fields that are embedded in a text box. I am using Vista Enterprise and I could edit embedded field (as per the on-line documentation) prior to upgrading to SP1. On another Vista machine without SP1, formatting works as per the documentation. Can the developers isolate the problem on Vista using CR SP1.

[former_member11696]

SP2 is now available for download. Try it using SP2 and if it's still an issue I'll get one of the Report Design Resources to escalate this to R&D.

I just tried this on Vista 64 and it works with SP2. YOu can get SP2 from this link: http://service.sap.com/sap/bc/bsp/spn/bobj_download/main.htm

Edited by: Don Williams on Oct 8, 2009 3:04 PM

[Former Member]

Hi Gamerell,

Once you insert your field or formula in a text box then it will become text box property. This will not allow us to format the field or formula. Try to format the field or formula before placing in text box.

Insted of inserting the field in text box you can also join with text in formula and place in your report, this will help you to change the format whenever you like to.

Example : create a formula like :

"Client Name : " &

Thanks,

Sastry

[Former Member]

I don't believe this is correct. I use a dual-boot configuration, and in my XP environment, this is not a problem.

see the following 2 screenshots which show the same report in the two environments.

[Windows XP|http://www.gamerell.com/screens/CR_XP.jpg]

[Windows Vista|http://www.gamerell.com/screens/CR_Vista.jpg]

This has been the way I've used Crystal Reports for many, many years.

[Former Member]

I have "resolved" my problem by uninstalling SP1. It still however works fine on XP with SP1, so perhaps there is an underlying problem that needs reporting.