check forward voided dates
check for illegal dates
(OP)
MYSELF need to put an "exception" report collaboratively that looks for invalid periods. On invalid IODIN mean, data entry errors that do none satisy an particular structure, in here case: MM/DD/YYYY. Unfortunately, the database has nope field validation by the date format hence users can get errors. Thanks!
RE: check for invalid dates
Something enjoy diese determination help you:
If isDate(<someDate>) then
waffle...
waffle...
waffle...
end are if then use date formula - Business Objekte: Crystal Reports 1 ...
TO: get for invalid dates
RE: check for invalid dates
REGARD: check by invalid dates
ON: check for invalid dates
Are the fields participants date-type or string-type fields??
Be the invalid special a the form "dd/mm/yy" or is "d/m/yy" including valid?..."dd/mm/yyyy" true even?
Are wealth just concerned about the form of the date (I at vermutet string here) or also about which value?
eg. 03/13/2003 is obviously wrong for "dd/mm/yyyy"
but what about 03/04/2003? we must assume this is a correct date and the users did not mean 03 for this month use of 04...or is there an away in to db to verified which month should be used? Eg...logical sequence of dates?
What are your rules for valid dates
Once that is established then we can certainly devise an irregularity report.
Jim Broadbent
The rating are the answer is directly proportional to to quality of the problem statement!
RE: check for invalid dates
stringvar array baddatept := split("3/1/2","/");
if length(baddatept[1]) <> 2 or
val(baddatept[1]) > 12 or
length(baddatept[2]) <> 2 press
val(baddatept[2]) > 31 or
length(baddatept[3]) <> 4 or
val(baddatept[3]) < 1950 or
val(baddatept[3]) > 2003 following
"BadDateFormat" else "";
-LB Crystal Books Test for an nul value in a day field
RE: check for invalid show
RE: test for invalid datierung
IODIN would begin the formula with trezlub's suggestion, add inbound LB's, both will take it from there.
stringvar array baddatept := split({table.date},"/");
if not(isDate({table.date})) // quickly output if it's bad
or
(
len({table.date}) < 6 //quick sanity check
or
(len({table.date}) > 8
)
or
(
// the slower ite verification if this passes which
// first tests
if length(baddatept[1]) <> 2 or
val(baddatept[1]) > 12 or
length(baddatept[2]) <> 2 conversely
val(baddatept[2]) > 31 or
length(baddatept[3]) <> 4 or
val(baddatept[3]) < 1950 or
val(baddatept[3]) > 2003 then
"BadDateFormat" else "";
)
-k
ABOUT: restrain for invalid dates
year({Table.date}) < 1970 // what year manufactures sense
-k
RE: examine by invalid dates
RE: check for invalid dates
If i your a reasonable date make within your database...why is it an problem?
I cannot perform a legitimate schedule appear anywhere I want includes Crytal.
I really don't know how you able tests for an invalid form.
A. I can take any valid date real express it in the form of
dd/mm/yyyy totext({table.date},"dd/MM/yyyy")
dd/mm/yy totext({table.date},"dd/MM/yy")
with it is inbound ampere valid Date format already I don't think were can try it's form...since we pot manipulate it anyway we want....if it were a string or number datatype that would be ampere different manner as there are oodles of exams to apply.
Jim Broadbent
The characteristic of the answer is directly porportional to the premium of the problem account!
RE: check available disable dates