I have a dbf table that contains one record with various fields that an administrator of my database can set. Some of the fields are a numeric "number of days" type field which will be used to calculate a date that a warning should start being sent to users that a deadline is approaching. Currently I get the values of these fields in my LoginProcessing.A5W page and then set session variables. I've been able to use these as arguments to filter grids. However, in order to display my new calculated date in my grid (which will be different for each row in the grid) I've had to use javascript to force the right value to display in the grid. This is fine except that the user can't search on this field in the grid. This turns out to be a problem. I've experimented with changing the column to a calculated field and it seems I can't search on fields in a grid that are calculated as part of the grid definition (not calculated fields from the query -- I can't do that either because I can't use session variables in calculated fields in a query).
First, am I correct that a column in a grid that is set through javascript can't be searched?
Second, am I correct that a calculated field as defined in a grid (not the query definition) can't be searched by the user?
Third, is there a way to use session or page or global variables in a calculated field definition in the query definition for a grid?
Basically, I don't want to store these warning dates in my table because if the administrator changes the number of days to warn by, all those dates would need to be updated. I can't find hardly any information despite extensive searching on using calculated fields in queries or grids where you need a variable from a different, unrelated table. It seems that the possibility of using different types of variables exists but I don't know if it really is allowed or how to make it work.
I really appreciate any help you might be able to give!
Lisa
First, am I correct that a column in a grid that is set through javascript can't be searched?
Second, am I correct that a calculated field as defined in a grid (not the query definition) can't be searched by the user?
Third, is there a way to use session or page or global variables in a calculated field definition in the query definition for a grid?
Basically, I don't want to store these warning dates in my table because if the administrator changes the number of days to warn by, all those dates would need to be updated. I can't find hardly any information despite extensive searching on using calculated fields in queries or grids where you need a variable from a different, unrelated table. It seems that the possibility of using different types of variables exists but I don't know if it really is allowed or how to make it work.
I really appreciate any help you might be able to give!
Lisa