Report Design
 Crystal Reports Forum : Crystal Reports 9 through 2022 : Report Design
Message Icon Topic: Crystal Report crash Post Reply Post New Topic
Author Message
rp1234
Newbie
Newbie


Joined: 15 Dec 2011
Online Status: Offline
Posts: 4
Quote rp1234 Replybullet Topic: Crystal Report crash
     Posted: 09 Jan 2013 at 2:29pm
Hi,

I need help.

I am running a crystal report for the days like Jan 1 to Jan 3rd.

Now i know there is a bad data for Jan 2nd.

So when i run the crystal report from Jan 1 to 3. Crystal Report crash while reading records.

My question is how can i skip a bad data while crystal report reading records so that it do not crash again.

In this case i know there is a bad data for Jan 2. But is there i can tell crystal Report to skip any bad data if you find it then skip it and keep reading records.

thx
Raj

IP IP Logged
Sastry
Moderator
Moderator
Avatar

Joined: 16 Jul 2012
Online Status: Offline
Posts: 537
Quote Sastry Replybullet Posted: 09 Jan 2013 at 10:59pm
Hi

Normally, crystal reports reads all your data tables and filters the records based on your filter conditions (it can be Add Command where / report level filters) then it will display the data in your report.

I don't think you have such options in crystal reports.
Thanks,
Sastry
IP IP Logged
DBlank
Moderator
Moderator


Joined: 19 Dec 2008
Online Status: Offline
Posts: 9053
Quote DBlank Replybullet Posted: 10 Jan 2013 at 3:59am
IMO you might be able to write exclusionary statements on 'bad data' if it is bad based on conversion process. These fails usually happens when you are converting a field data type and then selecting on the conversion formula, for example a numeric string converted to a numeric field or string as a date converted to an actual date field.
You can start the select process with a statement to weed out the items that fail the conversion process.
isnumeric(field) and ...
isdate(field) and ....
IP IP Logged
lockwelle
Moderator
Moderator


Joined: 21 Dec 2007
Online Status: Offline
Posts: 4374
Quote lockwelle Replybullet Posted: 10 Jan 2013 at 6:23am
to throw my ideas in..
 
if your data has ids, you could use a command to get the ids for Jan2 and then try filtering them out in the selection criteria.
 
and there is my old standby favorite...use a stored procedure, you can put as much code as you want to filter out the 'bad data', though you might need to go in and revise your stored proc...or leave the code in to 'catch' future bad data.
 
Otherwise, I think you would need to go the route of DBlank and put in logic into the report to try and prevent the bad data from crashing the report.
 
HTH
IP IP Logged
rp1234
Newbie
Newbie


Joined: 15 Dec 2011
Online Status: Offline
Posts: 4
Quote rp1234 Replybullet Posted: 10 Jan 2013 at 2:09pm
thx all for your reply.

i will try tonight.
IP IP Logged
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum