>Hi, Gnana-
>
>I don't know how your data is structured, of course, but it sounds to me like you are trying to print a cross-tab report of your data? Have you looked at the cross-tab wizard to get you started?
>

I'd forgotten about the cross-tab wizard; in most cases, the procedural code I put in my reply is just as easy as dealing with a wizard (especially after doing this report or it's (im)moral equivalent a hundred million times!)

If you attended the session on OLAP at DevCon, this type of reporting is exactly where OLAP would pay off big time, especially if the definition of a week were more complex, and you had many different views of the data that all needed the week perspective of sales - define a dimension in an OLAP data cube using the week definition, and then use the OLAP data cube for reporting. I do similar sorts of things now during my month-end, programmatically creating summary tables which are then used for analysis, both for end-of-month reports, and when people need to look at the static presentations of past data. Doing the pre-processing makes the summary data available to them quickly, but it requires a programmer's intervention to create a new way of correlating the data. With OLAP, the end-user could build their own data cubes, or use ones that've been previously created and add dimensions without affecting the other people using old format summaries, or getting someone to write a new analysis routine for them.

Something we can look forward to in an upcoming release of VFP I'd expect, and something that's available now to people using data in SQL Server, since OLAP capabilities are bundled with SQL Server now. The DevCon presentation certainly implied that OLAP is a key technology for Microsoft's databases, and it'd make life a whole lot easier for all of us, regardless of what data engine we use...