I am still working on my databases of team schedules, which almost works right, but there is one little glitch that I cannot get through except through an awkward kludge. The database opens with a team schedule, which is a matrix. The dates are variables date1, date2, … which are variables set up when the .initialize procedure runs. They are displayed as datepattern(datavalue(“date” + str(info(“MatrixCell”) + val(offset))),“Mon dd, 'yy”). The formula is what displays when the matrix is first opened, even after a showpage command. However, if I move up or down the database, the dates show up properly.
So far, the only way I can avoid this is to move up or down a record and then move back. But there should be an easier way to do this. The awkwardness comes from having to test whether moving the record is stopped or not.