[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

4160.0. "cal$set_date " by TROOA::DROSE () Thu May 12 1994 14:09

    
    Hi,
    
    A quick question regarding CAL$SET_DATE
    
    ;;DATE1;;
    /VALID=CAL$SET_DATE:"DATE1"
    
    Is the "DATE1" required?  I've noticed that a date entered in MM/DD/YY
    is converted to DD-MMM-YYYY and put back into the DATE1 field.
    
    If I dont specify "DATE1" then DATE1 is remains in the MM/DD/YY format.
    
    ;;DATE1;;    
    /VALID=CAL$SET_DATE
    
    So is the field name name required for CAL$SET_DATE?
    
    Thanks,
    Dan
    
T.RTitleUserPersonal
Name
DateLines
4160.1Symbol after CAL$SET_DATE is optionalIOSG::MARSHALLA glitch in realityThu May 12 1994 17:5314
/VALID=CAL$SET_DATE will validate the date in the current field.

/VALID=CAL$SET_DATE:symbol will validate the date in the current field, and
put the validated date into the specified symbol, which can be any symbol you
like, not necessarily the current field name.  As you have observed,
CAL$SET_DATE may change the date format when doing this.

You can also do something like:

GET CAL$SET_DATE:#symbol.%whole["TODAY +1W"]

to get the date a week from today, etc...

Scott