Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Active database table for Report Generation
Message
 
 
To
11/09/1999 18:51:52
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Miscellaneous
Thread ID:
00263717
Message ID:
00263723
Views:
22
You don't need to qualify the field names if you select the table. Capitization is ignored and is just for readability.

Interesting that you say "the summary table that I create and use in the report". Does this mean that you are create the report in the dataenvironment of the report? Or instead are all you selects and other report prep done in a PRG or form method, then you call the report?

*Make sure you remove any database tables from your report dataenvironment.*

What I do with reports is
- use a form to collect all the parameters (report start and end date, etc)
- call the report using REPORT FORM cEvan TO PRINTER PROMPT
- in the init method of the report environment I then open the tables I need (or use the forms dataenvironment), run all of my selects which finally end up in one cursor called cReport. The last statement at the end of this method is SELECT cReport
- in the destroy method close all cursors

If this doesn't help, recreate a simplified report, with tables and prgs as necessary that only has one field on the report. Ensure that this reproduces the error and email it to me (report file, dbf and other files) at evandelay@evandelay.com

>Evan, the varname on the field in the report is cntramt. I don't have it prefixed with an alias however the name is the same in both the first temporary table and the summary table that I create and use in the report. Could that be the problem? I thought that since my report was only using the second table that I didn't have to qualify the field names (ie. only one table active so no need to qualify).
>
>In your example you capitalize the first letter of each word in the field name. Does case actually differentiate two fields with the same name?
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform