It seems that a huge difference between Q&A and Sesame is that in Q&A, you could easily change the design of a report on the fly whereas in Sesame, you must hard code the report with specific fields or with unbound fields.

For instance, we have a master report in Q&A that is set up to generate a performance summary for a particular month.  The fields selected are not date fields but rather number fields.  In Q&A, we change the temporary design to select the fields pertaining to the relevant month.

It appears in Sesame that I have to hard code the report for each month resulting in 12 reports.  This is very time consuming, even though I do copy the report layout and modify it.  There's no guess work for the users but it creates long term maintenance issues in terms of modifying reports.

I started trying to program some of the unbound fields but wasn't getting the result I wanted.

Do you see another opportunity in dealing with this ?

Thanks,

Louis

The form is setup with a section of rows and columns as per this example:

Month | Field1| Field2| Field3|, etc

JAN     |
FEB     |
MAR    |
etc.

For Jan, I would pick up all the fields across the row.  Same for Feb thru Dec.

If there is way to program the unbound fields to capture this info, it would be a big timesaver.

Thanks

Louis

For LEs that hold numbers for a particular period, try this:

Suppose you had End Of Month balances for every month for every year on a form with the current balance in the LE for the current MY.

LE names should be formatted to include "F" as a prefix, a number for month and last 2 digits for year. Like this:

Jan/2005 = F105
Feb/2005 = F205
Sep/2006 = F906
Dec/2007 = F1207

Make the Report element have a formula to call the spedific LE by using @FIELD(), something like this:

var vMonthOffset as INT
vMonthOffset=0

@FIELD("F" + @STR(@MONTH(@DATE)-vMonthOffset) + @STR(@MID(@DATE,3,2)) )

------------------------------------------
What this does is actually brings up a different LE value; each month bringing up the current LE name (FMYY), but could bring up LEs from other months by changing an Offset value.  Add a suffix (A,B,C?) for each additional field across the form to take care of your three fields.  Put the diffeent formula in each of the three unbound fields on the report.
-----------------------------------
Per my previous posting you could make more complex with variables for offsetting the year, you could provide prompts and them converted into an offset value.

Note again: code above is untested using techniques I have used in Q&A over past years.  In Q&A I made a Derived Column for the Offset value.  So, when making TEMP changes to a report, only had to change the single offset value in the Derived Column section.

Seems like forever since you sent me your response.  With holidays, a busy work schedule, trying to absorb your example and a little bit of procrastination, I have not been able to implement your fine example.

I read with interest your comment about embedding the Pop Up menu right int the report - this would definitely be preferable and I look forward to this in a future release.  Any idea when ?

In the meantime, within the same spreadsheet, I have another section setup similarly.  This would mean two command buttons in the database.  Is this feasible ?

Thanks,

Louis

I was able to incorporate your demo into my database with some minor modifications and it worked like a charm !

It looks like I will need about 6 command buttons to deal with different reports, so I have set up a "Command Centre" on my database to keep all the buttons in one central place.

I went through the same steps to create another command button and report, and I am having a problem with the program as it does not recognize "sMonth".  It is able to run the report utilizing the popup menu but the the first key number field is not coming up with any value for any month.

It appears I have mapped the LE's correctly to pick up the values.  I have placed reference to sMonth in the title also, and it does not recognize.  Would any of the programming have to change in the command button other than report name or in the Global Code ?

Any suggestions would help.  In the meantime I will keep reviewing.

Thanks,

Louis

This is what I have in my Global Code:

stat sMonth as string

sMonth = @Globalvalue("Reportmonth")

This is the exact coding that I placed in my first report which worked.

I do not get any errors in my progrma when I test it.

I do, however, receive a warning as the report layout element name has a     /     in it.

Thanks,

Louis

The command button has this statement in it.

I continued on and created a new report and it worked just fine.

The difference between the two reports that work and the one that doesn't is that there are more than one variable in the functional ones and only one variable in the the non-functional one.  Meaning, I only had to reference one field as per this sample:

IF sMonth = "JAN"
{
     LE61 = LE1
}
ELSE IF sMonth = "FEB"
{
     LE61 = LE12
}            


Does this make any difference ?

Thanks,

Louis

Good morning. 
It goes through all the motions and prints the report to HTML but does not pick up the required data for the COMM field nor the sMonth at the top of the report.

I think comes down to the programming not recognizing the sMonth.

I am going to try and re-create this one from scratch.  I am sure that it is just a minor mis-statement in my programming. 

Thanks,

Louis

Thanks,

Louis