Hello All, Thanks in advance for any help.

I have a report which is basically a form letter. This letter is from our
clients (known as clients) and to our client's clients (known as debtors).
The letter has to be signed by one of our staff (known as collectors).

I have a query results which contain the line items for each report sorted
by Client and within client by debtor.

I have the following relationships

SET RELATION TO CLI_CODE INTO CLIENTS
SET RELATION TO DEBT_CODE INTO DEBTORS ADDI
SET RELATION TO SUBSTR(DEBT_CODE, 1, 1) INTO COLLECTORS ADDI

The report specifies the client's address from the client table, and the
debtors address from the debtor table.

The problem is that the first page of the report does not contain all of the
address information for either the client or the debtor. Every other page is
fine.

If I use a FOR clause in the report command the first letter as missing
info. Every other one is fine.

If I insert a blank record into the table (which is readwrite and indexed by
cli_code + debt_code) the problem will occur on that first (blank) report
and then every other page will be fine.

I'm sure it is something simple and obvious that I'm overlooking but does
anyone have any ideas?

Thanks again,

Jeff

RE: Strange Report Problem with VFP 7.0 by Leemi

Leemi
Tue Aug 10 14:28:58 CDT 2004

Hi Jeff:

As best as I can understand your scenario, you are trying to create a
one-to many -to many (a multi child) report. The Visual FoxPro Report
Designer cannot create such a nested report. However, there are
workarounds to this limitation. Navigate to
http://fox.wikis.com/wc.dll?Wiki~MultiChildFoxProReports~VFP for one
solution. Also,
Cathy Pountney's book "The Visual FoxPro Report Writer: Pushing it to the
Limit and Beyond" has a technique you can use to simulate multiple detail
bands in the VFP Report Writer.

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 Public Beta Now Available!! --*
Download the VFP9 beta here: http://msdn.microsoft.com/vfoxpro/

*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003

>Hello All, Thanks in advance for any help.

>I have a report which is basically a form letter. This letter is from our
>clients (known as clients) and to our client's clients (known as debtors).
>The letter has to be signed by one of our staff (known as collectors).

>I have a query results which contain the line items for each report sorted
>by Client and within client by debtor.

>I have the following relationships

>SET RELATION TO CLI_CODE INTO CLIENTS
>SET RELATION TO DEBT_CODE INTO DEBTORS ADDI
>SET RELATION TO SUBSTR(DEBT_CODE, 1, 1) INTO COLLECTORS ADDI

>The report specifies the client's address from the client table, and the
>debtors address from the debtor table.

>The problem is that the first page of the report does not contain all of
the
>address information for either the client or the debtor. Every other page
is
>fine.

>If I use a FOR clause in the report command the first letter as missing
>info. Every other one is fine.

>If I insert a blank record into the table (which is readwrite and indexed
by
>cli_code + debt_code) the problem will occur on that first (blank) report
>and then every other page will be fine.

>I'm sure it is something simple and obvious that I'm overlooking but does
>anyone have any ideas?

>Thanks again,

>Jeff


Re: Strange Report Problem with VFP 7.0 by Jeff

Jeff
Tue Aug 10 14:41:10 CDT 2004

Lee,

Thanks for the feedback.

The relationships are all one-to-one but there are three of them:

Letters->Client (1-to-1)
Letters->Debtor (1-to-1)
Letters->Collectors (1-to-1)

Each Letter (Grouped by Client and Debtor) contains one or more records per
report but each records only points to a single client, a single debtor, and
a single collector on the expressions cli_code, debt_code, and
substr(debt_code,1,1) respectively.

The only thing that doesn't work is the first page of the report and what's
missing from that page is some but not all of the fields from both the
client and debtor tables.

Thanks again,

Jeff

"Lee Mitchell" <Leemi@online.microsoft.com> wrote in message
news:Et4XPBxfEHA.3636@cpmsftngxa06.phx.gbl...
> Hi Jeff:
>
> As best as I can understand your scenario, you are trying to create a
> one-to many -to many (a multi child) report. The Visual FoxPro Report
> Designer cannot create such a nested report. However, there are
> workarounds to this limitation. Navigate to
> http://fox.wikis.com/wc.dll?Wiki~MultiChildFoxProReports~VFP for one
> solution. Also,
> Cathy Pountney's book "The Visual FoxPro Report Writer: Pushing it to the
> Limit and Beyond" has a technique you can use to simulate multiple detail
> bands in the VFP Report Writer.
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 Public Beta Now Available!! --*
> Download the VFP9 beta here: http://msdn.microsoft.com/vfoxpro/
>
> *-- VFP8 HAS ARRIVED!! --*
> Read about all the new features of VFP8 here:
> http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
> Purchase VFP8 here:
> http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
> >Hello All, Thanks in advance for any help.
>
> >I have a report which is basically a form letter. This letter is from our
> >clients (known as clients) and to our client's clients (known as
debtors).
> >The letter has to be signed by one of our staff (known as collectors).
>
> >I have a query results which contain the line items for each report
sorted
> >by Client and within client by debtor.
>
> >I have the following relationships
>
> >SET RELATION TO CLI_CODE INTO CLIENTS
> >SET RELATION TO DEBT_CODE INTO DEBTORS ADDI
> >SET RELATION TO SUBSTR(DEBT_CODE, 1, 1) INTO COLLECTORS ADDI
>
> >The report specifies the client's address from the client table, and the
> >debtors address from the debtor table.
>
> >The problem is that the first page of the report does not contain all of
> the
> >address information for either the client or the debtor. Every other page
> is
> >fine.
>
> >If I use a FOR clause in the report command the first letter as missing
> >info. Every other one is fine.
>
> >If I insert a blank record into the table (which is readwrite and indexed
> by
> >cli_code + debt_code) the problem will occur on that first (blank)
report
> >and then every other page will be fine.
>
> >I'm sure it is something simple and obvious that I'm overlooking but does
> >anyone have any ideas?
>
> >Thanks again,
>
> >Jeff
>



Re: Strange Report Problem with VFP 7.0 by nw9952

nw9952
Tue Aug 10 15:06:54 CDT 2004

try command "locate" or "goto recno()"
just before you run report

al

"Jeff Grippe" <jgrippe@hilldun.com> wrote in message
news:10hi601piatrlba@news.supernews.com...
> Hello All, Thanks in advance for any help.
>
> I have a report which is basically a form letter. This letter is from our
> clients (known as clients) and to our client's clients (known as debtors).
> The letter has to be signed by one of our staff (known as collectors).
>
> I have a query results which contain the line items for each report sorted
> by Client and within client by debtor.
>
> I have the following relationships
>
> SET RELATION TO CLI_CODE INTO CLIENTS
> SET RELATION TO DEBT_CODE INTO DEBTORS ADDI
> SET RELATION TO SUBSTR(DEBT_CODE, 1, 1) INTO COLLECTORS ADDI
>
> The report specifies the client's address from the client table, and the
> debtors address from the debtor table.
>
> The problem is that the first page of the report does not contain all of
the
> address information for either the client or the debtor. Every other page
is
> fine.
>
> If I use a FOR clause in the report command the first letter as missing
> info. Every other one is fine.
>
> If I insert a blank record into the table (which is readwrite and indexed
by
> cli_code + debt_code) the problem will occur on that first (blank) report
> and then every other page will be fine.
>
> I'm sure it is something simple and obvious that I'm overlooking but does
> anyone have any ideas?
>
> Thanks again,
>
> Jeff
>
>



Re: Strange Report Problem with VFP 7.0 by Dan

Dan
Tue Aug 10 15:23:55 CDT 2004

After creating relations, you need to move the record pointer in the parent
table to "line up" all the children.

Usually a GO TOP will accomplish it.

Dan


Jeff Grippe wrote:
> Hello All, Thanks in advance for any help.
>
> I have a report which is basically a form letter. This letter is from
> our clients (known as clients) and to our client's clients (known as
> debtors). The letter has to be signed by one of our staff (known as
> collectors).
>
> I have a query results which contain the line items for each report
> sorted by Client and within client by debtor.
>
> I have the following relationships
>
> SET RELATION TO CLI_CODE INTO CLIENTS
> SET RELATION TO DEBT_CODE INTO DEBTORS ADDI
> SET RELATION TO SUBSTR(DEBT_CODE, 1, 1) INTO COLLECTORS ADDI
>
> The report specifies the client's address from the client table, and
> the debtors address from the debtor table.
>
> The problem is that the first page of the report does not contain all
> of the address information for either the client or the debtor. Every
> other page is fine.
>
> If I use a FOR clause in the report command the first letter as
> missing info. Every other one is fine.
>
> If I insert a blank record into the table (which is readwrite and
> indexed by cli_code + debt_code) the problem will occur on that
> first (blank) report and then every other page will be fine.
>
> I'm sure it is something simple and obvious that I'm overlooking but
> does anyone have any ideas?
>
> Thanks again,
>
> Jeff



Re: Strange Report Problem with VFP 7.0 by Jeff

Jeff
Tue Aug 10 15:35:10 CDT 2004

Dan,

Thank you for the help. I thought for sure that your suggestion was going to
work but I still have the problem and only with the first record in the
report.

When I look at the fields using BROWSE there is no display problem.

The problem only occurs on the first record of the report and not with all
of the fields.

I'm stumped by this one.

My workaround is to insert a blank record and throw away the first page
which is simple enough but I'd love to know what is going on here.

Thanks again,

Jeff
"Dan Freeman" <spam@microsoft.com> wrote in message
news:uHLPKfxfEHA.1356@TK2MSFTNGP09.phx.gbl...
> After creating relations, you need to move the record pointer in the
parent
> table to "line up" all the children.
>
> Usually a GO TOP will accomplish it.
>
> Dan
>
>
> Jeff Grippe wrote:
> > Hello All, Thanks in advance for any help.
> >
> > I have a report which is basically a form letter. This letter is from
> > our clients (known as clients) and to our client's clients (known as
> > debtors). The letter has to be signed by one of our staff (known as
> > collectors).
> >
> > I have a query results which contain the line items for each report
> > sorted by Client and within client by debtor.
> >
> > I have the following relationships
> >
> > SET RELATION TO CLI_CODE INTO CLIENTS
> > SET RELATION TO DEBT_CODE INTO DEBTORS ADDI
> > SET RELATION TO SUBSTR(DEBT_CODE, 1, 1) INTO COLLECTORS ADDI
> >
> > The report specifies the client's address from the client table, and
> > the debtors address from the debtor table.
> >
> > The problem is that the first page of the report does not contain all
> > of the address information for either the client or the debtor. Every
> > other page is fine.
> >
> > If I use a FOR clause in the report command the first letter as
> > missing info. Every other one is fine.
> >
> > If I insert a blank record into the table (which is readwrite and
> > indexed by cli_code + debt_code) the problem will occur on that
> > first (blank) report and then every other page will be fine.
> >
> > I'm sure it is something simple and obvious that I'm overlooking but
> > does anyone have any ideas?
> >
> > Thanks again,
> >
> > Jeff
>
>



Re: Strange Report Problem with VFP 7.0 by Jeff

Jeff
Wed Aug 11 08:36:10 CDT 2004

Thanks for the suggestion.

I did exactly that so all of the data is in a single cursor with no more
relationships.

The problem still occurs with record 1.

This appear to not be a data drive problem (or at least not a "set relation"
driven problem but rather something strange with this report itself.

The report is nothing special. It doesn't do any cute "multipass" stuff or
anything esoteric. It is basically just a batch of form letters with line
items and a total.

I'm going to try creating the report again from scratch to see if something
odd found its way into the report file.

Any other suggestions welcome and appreciated.

Thanks
"Tom Norwood" <TomNorwood@discussions.microsoft.com> wrote in message
news:EB018F04-0F2C-4C5E-8F0F-7EB7AD350A6A@microsoft.com...
> Why don't you SELECT all the data you need into a cursor and use that as
the
> record source for the report?
>
> "Jeff Grippe" wrote:
>
> > Dan,
> >
> > Thank you for the help. I thought for sure that your suggestion was
going to
> > work but I still have the problem and only with the first record in the
> > report.
> >
> > When I look at the fields using BROWSE there is no display problem.
> >
> > The problem only occurs on the first record of the report and not with
all
> > of the fields.
> >
> > I'm stumped by this one.
> >
> > My workaround is to insert a blank record and throw away the first page
> > which is simple enough but I'd love to know what is going on here.
> >
> > Thanks again,
> >
> > Jeff
> > "Dan Freeman" <spam@microsoft.com> wrote in message
> > news:uHLPKfxfEHA.1356@TK2MSFTNGP09.phx.gbl...
> > > After creating relations, you need to move the record pointer in the
> > parent
> > > table to "line up" all the children.
> > >
> > > Usually a GO TOP will accomplish it.
> > >
> > > Dan
> > >
> > >
> > > Jeff Grippe wrote:
> > > > Hello All, Thanks in advance for any help.
> > > >
> > > > I have a report which is basically a form letter. This letter is
from
> > > > our clients (known as clients) and to our client's clients (known as
> > > > debtors). The letter has to be signed by one of our staff (known as
> > > > collectors).
> > > >
> > > > I have a query results which contain the line items for each report
> > > > sorted by Client and within client by debtor.
> > > >
> > > > I have the following relationships
> > > >
> > > > SET RELATION TO CLI_CODE INTO CLIENTS
> > > > SET RELATION TO DEBT_CODE INTO DEBTORS ADDI
> > > > SET RELATION TO SUBSTR(DEBT_CODE, 1, 1) INTO COLLECTORS ADDI
> > > >
> > > > The report specifies the client's address from the client table, and
> > > > the debtors address from the debtor table.
> > > >
> > > > The problem is that the first page of the report does not contain
all
> > > > of the address information for either the client or the debtor.
Every
> > > > other page is fine.
> > > >
> > > > If I use a FOR clause in the report command the first letter as
> > > > missing info. Every other one is fine.
> > > >
> > > > If I insert a blank record into the table (which is readwrite and
> > > > indexed by cli_code + debt_code) the problem will occur on that
> > > > first (blank) report and then every other page will be fine.
> > > >
> > > > I'm sure it is something simple and obvious that I'm overlooking but
> > > > does anyone have any ideas?
> > > >
> > > > Thanks again,
> > > >
> > > > Jeff
> > >
> > >
> >
> >
> >