Ted, I've used Sys(2015) for a long time in all my apps for temporary cursors and I've never had a problem so I'm very interested in the fact you say that invalid cursor names can be returned. When and under what circumstances?
I do agree however that reports should be pre-processed with SQL Selects in order to produce a single cursor when possible. Dave Crozier -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Roche Sent: 13 June 2006 21:02 To: [email protected] Subject: Re: Table and field name reference in report On 6/13/06, James E. Harvey <[EMAIL PROTECTED]> wrote: > How do you refer to a table that is assigned a name created with the > sys(2015) function, in the report designer? > I don't. SYS(2015) can produce invalid alias/table names, and there hasn't been a reason to do this since Fox 2.x. Instead, give the cursor an alias, like FRXOutput. > This is a report with two data groupings and two detail bands > > Code example***** > LCDBF = sys(2015) && mares > Select mare, name from mastmare into table &lcdbf nofilter > Report form hsrp_mare to print prompt preview > *** > SELECT mare, name from mastmare into cursor hsrp_mare in the report, you refer to the fields as hsrp_mare.name _or_ even better is to drop the cursor name reference altogether, if your report is only using one table (a Best Practice when practical) -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
