Calculated Field In Report

#51

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

Quote:

I set it in quotes because it can happen. I haven't found out when it
happens, though.

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

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

Quote:

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:

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!

#52

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

Quote:

I set it in quotes because it can happen. I haven't found out when it
happens, though.

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

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

Quote:

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:

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!

#53

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

Quote:

I set it in quotes because it can happen. I haven't found out when it
happens, though.

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

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

Quote:

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:

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!

#54

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

Quote:

I set it in quotes because it can happen. I haven't found out when it
happens, though.

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

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

Quote:

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:

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!

#55

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

Quote:

I set it in quotes because it can happen. I haven't found out when it
happens, though.

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

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

Quote:

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:

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!

#56

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

Quote:

I set it in quotes because it can happen. I haven't found out when it
happens, though.

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

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

Quote:

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:

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!

#57

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

Quote:

I set it in quotes because it can happen. I haven't found out when it
happens, though.

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

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

Quote:

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:

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!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Calculated Field In Report

comp.databases.paradox comp.databases.paradox

Re: Calculated Field In Report - 03-12-2008 , 03:37 PM

Re: Calculated Field In Report - 03-12-2008 , 03:37 PM

Re: Calculated Field In Report - 03-12-2008 , 03:37 PM

Re: Calculated Field In Report - 03-12-2008 , 03:37 PM

Re: Calculated Field In Report - 03-12-2008 , 03:37 PM

Re: Calculated Field In Report - 03-12-2008 , 03:37 PM

Re: Calculated Field In Report - 03-12-2008 , 03:37 PM