dbTalk Databases Forums  

Calculated Field In Report

comp.databases.paradox comp.databases.paradox


Discuss Calculated Field In Report in the comp.databases.paradox forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Willard Hoppe
 
Posts: n/a

Default Calculated Field In Report - 03-11-2008 , 03:32 PM







I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!



Reply With Quote
  #2  
Old   
Bertil Isberg
 
Posts: n/a

Default Re: Calculated Field In Report - 03-11-2008 , 04:14 PM






<<

Is this normal behavior?
Quote:
Yes, this "can" be normal behaviour if the strucure of the table has changed
after the report was created.


--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Willard Hoppe" <billh (AT) nospam (DOT) brra.com> skrev i meddelandet
news:47d6fa72$1 (AT) pnews (DOT) thedbcommunity.com...
Quote:
I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!





Reply With Quote
  #3  
Old   
Bertil Isberg
 
Posts: n/a

Default Re: Calculated Field In Report - 03-11-2008 , 04:14 PM



<<

Is this normal behavior?
Quote:
Yes, this "can" be normal behaviour if the strucure of the table has changed
after the report was created.


--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Willard Hoppe" <billh (AT) nospam (DOT) brra.com> skrev i meddelandet
news:47d6fa72$1 (AT) pnews (DOT) thedbcommunity.com...
Quote:
I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!





Reply With Quote
  #4  
Old   
Bertil Isberg
 
Posts: n/a

Default Re: Calculated Field In Report - 03-11-2008 , 04:14 PM



<<

Is this normal behavior?
Quote:
Yes, this "can" be normal behaviour if the strucure of the table has changed
after the report was created.


--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Willard Hoppe" <billh (AT) nospam (DOT) brra.com> skrev i meddelandet
news:47d6fa72$1 (AT) pnews (DOT) thedbcommunity.com...
Quote:
I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!





Reply With Quote
  #5  
Old   
Bertil Isberg
 
Posts: n/a

Default Re: Calculated Field In Report - 03-11-2008 , 04:14 PM



<<

Is this normal behavior?
Quote:
Yes, this "can" be normal behaviour if the strucure of the table has changed
after the report was created.


--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Willard Hoppe" <billh (AT) nospam (DOT) brra.com> skrev i meddelandet
news:47d6fa72$1 (AT) pnews (DOT) thedbcommunity.com...
Quote:
I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!





Reply With Quote
  #6  
Old   
Bertil Isberg
 
Posts: n/a

Default Re: Calculated Field In Report - 03-11-2008 , 04:14 PM



<<

Is this normal behavior?
Quote:
Yes, this "can" be normal behaviour if the strucure of the table has changed
after the report was created.


--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Willard Hoppe" <billh (AT) nospam (DOT) brra.com> skrev i meddelandet
news:47d6fa72$1 (AT) pnews (DOT) thedbcommunity.com...
Quote:
I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!





Reply With Quote
  #7  
Old   
Bertil Isberg
 
Posts: n/a

Default Re: Calculated Field In Report - 03-11-2008 , 04:14 PM



<<

Is this normal behavior?
Quote:
Yes, this "can" be normal behaviour if the strucure of the table has changed
after the report was created.


--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Willard Hoppe" <billh (AT) nospam (DOT) brra.com> skrev i meddelandet
news:47d6fa72$1 (AT) pnews (DOT) thedbcommunity.com...
Quote:
I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!





Reply With Quote
  #8  
Old   
Bertil Isberg
 
Posts: n/a

Default Re: Calculated Field In Report - 03-11-2008 , 04:14 PM



<<

Is this normal behavior?
Quote:
Yes, this "can" be normal behaviour if the strucure of the table has changed
after the report was created.


--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Willard Hoppe" <billh (AT) nospam (DOT) brra.com> skrev i meddelandet
news:47d6fa72$1 (AT) pnews (DOT) thedbcommunity.com...
Quote:
I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!





Reply With Quote
  #9  
Old   
Willard Hoppe
 
Posts: n/a

Default Re: Calculated Field In Report - 03-11-2008 , 09:28 PM




I've used this report and table unchanged for years, and then suddenly there
was an issue. I always remember to make sure the fields are exactly as they
were, but must have forgot this time.

Did you put the word can in "quotes" because this isn't a proper way of doing
this?

Should the report be re-saved every once in a while?

Any additional thoughts you might have would be appreciated.





"Bertil Isberg" <ctech (AT) corel (DOT) ca> wrote:
Quote:

Is this normal behavior?


Yes, this "can" be normal behaviour if the strucure of the table has changed

after the report was created.


--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Willard Hoppe" <billh (AT) nospam (DOT) brra.com> skrev i meddelandet
news:47d6fa72$1 (AT) pnews (DOT) thedbcommunity.com...

I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made
the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!






Reply With Quote
  #10  
Old   
Willard Hoppe
 
Posts: n/a

Default Re: Calculated Field In Report - 03-11-2008 , 09:28 PM




I've used this report and table unchanged for years, and then suddenly there
was an issue. I always remember to make sure the fields are exactly as they
were, but must have forgot this time.

Did you put the word can in "quotes" because this isn't a proper way of doing
this?

Should the report be re-saved every once in a while?

Any additional thoughts you might have would be appreciated.





"Bertil Isberg" <ctech (AT) corel (DOT) ca> wrote:
Quote:

Is this normal behavior?


Yes, this "can" be normal behaviour if the strucure of the table has changed

after the report was created.


--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Willard Hoppe" <billh (AT) nospam (DOT) brra.com> skrev i meddelandet
news:47d6fa72$1 (AT) pnews (DOT) thedbcommunity.com...

I use Paradox 7.

I have a calculated field in a report as follows:
[INCENTVE.City] + ", " + [INCENTVE.State] + " " + [INCENTVE.Zip]

Obviously the data is drawn from the

CITY
STATE
ZIP
fields in my database.

However, if the fields are not in the exact same order as when I made
the
report, there are issues.

For example, if the fields are in the following order in the table

CITY
ZIP
STATE

The report will print:

TRENTON 08648 NJ


Is this normal behavior?

Thanks in advance!






Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.