Need to limit entry in field ONLY IF original entry is not older than 7 days. Help Please!

[Fulltimer]

I have several fields (character) that should only be modified within seven days of their original creation (ie. new record).

I want to create an ENABLE/DISABLE client side condition based on the date of another date field (ie. datecreated).

Puesdo code would be as:

if datecreated is within the last week, allow (ie. enable) editing to the LASTNAME field.

I've had some success with code similar to:

DATECREATED < DATE() - but this is always true.

This is what I am trying to do:

DATECREATED > ( DATE() -7 )

This never evaluates to true. The -7 is the killer. Seems logical but Javascript doesn't like it.

If you can help with some tested code, it would really be appreciated.

[TheSmitchell]

Re: Need to limit entry in field ONLY IF original entry is not older than 7 days. Help Please!

You want to compare dates, so you'll need to do javascript date math
http://stackoverflow.com/questions/3...to-todays-date

var sevenDaysAgo = function ()
{
    var d = new Date();
    // getDate: gets the date in days
    // setDate: sets the date in days (so you can add or sub any number of days here)
    d.setDate(d.getDate() - 7)

    return d;
}

You'll probably also need to parse your "DATECREATED" value - I think Alpha gives you a string when you call {grid.object}.getValue('G',rowNum,'DATECREATED')

var getDateCreated = function (rowNum)
{
    var c = {grid.object}.getValue('G',rowNum,'DATECREATED');

    // If your DATECREATED is in the format MM/dd/YYYY...
    // split: changes c from "MM/dd/YYYY" into an array ["MM","dd","YYYY"]
    // EG: "01/12/1985" becomes ["01","12","1985"]
    c = c.split("/"); 

    // Months in javascript are zero indexed. EG, January = 0, Feburary = 1, and so on and so fourth
    // The Date constructor: Date(Year,Month,Day)
    var asD = new Date(c[2],c[0]-1,c[1]);

    return asD;
}

Putting it all together

var canEdit = function (rowNum)
{
    var created = getDateCreated(rowNum);
    var cutOff = sevenDaysAgo();

    return created >= cutoff;
}

---
Sarah

[christappan]

Re: Need to limit entry in field ONLY IF original entry is not older than 7 days. Help Please!

Sarah's solution will work, but as another option, I've started putting things like this in the query itself sometimes. In your SELECT statement, include a column something like this:

SELECT *, IF(DATECREATED > AddDaysToDate(CurrentDATE(), -7),'Yes','No') AS Editable
FROM ...

Then put the "Editable" column in your grid/detail view/whatever, hide it, and the enable expression in the key fields to Editable="Yes"

[aburningflame]

Re: Need to limit entry in field ONLY IF original entry is not older than 7 days. Help Please!

+1 for chris's answer - We use this exact same method. I believe Chris's looks like SQL server.
We dont use an IF to return 'yes','no', just let MySQL/SQL return a boolean - In chris's example take away the IF and the YES,NO.
Below will return 1 if it is editable and 0 if it is not (logical values).

Put the editable column in your grid and hide it.
Enable Expression: editable=1

In MYSQL it would look something like: SELECT tablename.*, DATEDIFF(CURDATE(),created_on)<7 as editable FROM tablename
Are they allowed to edit it on the 7th day? If yes, change the above to <=7

[TheSmitchell]

Re: Need to limit entry in field ONLY IF original entry is not older than 7 days. Help Please!

The SQL method works - I've done this a few times. But doing it in the query means your server is doing all the work calculating the outcome instead of the client's web browser. Of course, maybe this is a calculation that is best left to be done server-side altogether, since you reeeeeally want to prevent people from editing records older than a certain date. If that's the case, server-side validation may be in order to prevent the user from editing the fields & submitting them through other means - eg, FireBug.

[aburningflame]

Re: Need to limit entry in field ONLY IF original entry is not older than 7 days. Help Please!

The SQL method works - I've done this a few times. But doing it in the query means your server is doing all the work calculating the outcome instead of the client's web browser.

The calculation performed on the server side is a very negligible server hit. The MySQL/SQL Server engines are perfectly capable of doing this calculation for thousands of records in milliseconds - not a big deal.

Of course, maybe this is a calculation that is best left to be done server-side altogether, since you reeeeeally want to prevent people from editing records older than a certain date. If that's the case, server-side validation may be in order to prevent the user from editing the fields & submitting them through other means - eg, FireBug.

+1 - If its an internal app I wouldnt worry about it too much. If you are concerned some employee might be using Firebug to edit stuff they are not allowed to then override the CanUpdateRecord method - just to be safe I recommend adding the code into CanUpdateRecord anyways to prevent unauthorized edits.

'Set to cancel right away - This will REJECT all updates UNLESS the condition is met 
'Example: (If you cant properly load whether or not it is editable - you should error out and not let them edit it)

Result.Cancel=.t.
Result.ErrorHTML="You cannot edit this record - it has been 7 days since the records creation"

'code to calculate editable

IF editable THEN
  Result.Cancel=.f.
  Result.ErrorHTML=""
END IF