Duplicate Records on Filter

[JK]

Hi,

I'm getting a very strange error: I have a report that is displaying
records multiple times when I view it. When I look at the record
source of the report and run the query, I get the expected results
(listing each record once). If though, I limit the query (e.g. WHERE
CustomerID = 1), either by using a WHERE clause in the query, or a
Filter on the report, the results show two records for CustomerID 1.
When I look in the table though, there is only one record for
CustomerID 1.

Anyone had any experience with something like this?

Any help would be greatly appreciated.

Thanks!
JK

 

[Allen Browne]

Post the SQL statement, including the WHERE CustomerID = 1.

 

[JK]

Allen,

(the CustomerID = 1 was a generic statement)

Here is my original query:
SELECT tblCommitmentsFundSource.*, qryFData.*
FROM (tblCommitmentsFundSource LEFT JOIN tblBudgetProposed ON
(tblCommitmentsFundSource.Description = tblBudgetProposed.Description)
AND (tblCommitmentsFundSource.BudgetItem =
tblBudgetProposed.BudgetItem) AND (tblCommitmentsFundSource.SubGroup =
tblBudgetProposed.SubGroup) AND (tblCommitmentsFundSource.Group =
tblBudgetProposed.Group) AND (tblCommitmentsFundSource.Country =
tblBudgetProposed.Country)) LEFT JOIN qryFData ON
tblBudgetProposed.ProgramSubElementID = qryFData.ProgramElementID;

This returns all records - I'm using the record with ID # 14992 as an
example. It appears in this query (and report) once.

Then, when I have this query:
SELECT tblCommitmentsFundSource.*, qryFData.*
FROM (tblCommitmentsFundSource LEFT JOIN tblBudgetProposed ON
(tblCommitmentsFundSource.Description = tblBudgetProposed.Description)
AND (tblCommitmentsFundSource.BudgetItem =
tblBudgetProposed.BudgetItem) AND (tblCommitmentsFundSource.SubGroup =
tblBudgetProposed.SubGroup) AND (tblCommitmentsFundSource.Group =
tblBudgetProposed.Group) AND (tblCommitmentsFundSource.Country =
tblBudgetProposed.Country)) LEFT JOIN qryFData ON
tblBudgetProposed.ProgramSubElementID = qryFData.ProgramElementID
WHERE (((tblCommitmentsFundSource.ObligationID)=14992));

The results show record 14992 twice. Record 14992 only appears in the
tblCommitmentsFundSource table once, and due to the Left Joins, I
don't see how it could appear twice in the results. I also can't
understand how the simple addition of a WHERE clause could cause this.

Any suggestions?

Thanks!
JK

 

[Allen Browne]

Okay, it's a bit hard to tell for sure, as there seems to be another query
involved in the source, but my guess it the way Access is interpreting the
left joins. (Presumably you have already tried a compact/repair, to
eliminate the possibility of a bad index.)

IME, Access ignores the brackets in the FROM statement. This is despite the
fact that:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed) LEFT JOIN
qryFData
would give different results than:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
(We are omitting the ON clause for simplicity.)

For example, say:
- tblCommitmentsFundSource generates 1 record for ID #14492,
- tblBuggetProposed generates no record for ID #14492,
- qryFData generates 2 records for ID #14492.
Then:
(tblBuggetProposed LEFT JOIN qryFData)
would generate *no* record for ID #14492, and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate *one* record for ID #14492.

But:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed)
would geneate one record for ID #14492,
and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate 2 records for ID #14492.

So, presumably the WHERE clause is causing the query optimizer to change the
execution plan.

To be honest, I'm half asleep ATM, but if you want to investigate whether a
change of query plan really is causing the results you are seeing, these
links may help:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacbk02/html/odc_4009c15.asp
http://builder.com.com/5100-6388-5064388.html
http://msdn.microsoft.com/archive/d...MicrosoftAccessMicrosoftJetDatabaseEngine.asp

If you happen to be using Access 2007, the reg setting is:
[HKLM\SOFTWARE\Microsoft\Office\12.0\Access Connectivity
Engine\Engines\Debug] "JETSHOWPLAN"="ON"

 

[JK]

Allen,

I really appreciate your help on this.

Yes, I had tried a Compact/Repair, but that didn't fix it.

FYI: The query (qryFData) is simply a query that combines a few lookup
tables. tblCommitmentsFundSource has a field called
ProgramSubElementID that holds an ID value of a record in qryFData.
There is one and only one ProgramSubElementID in that query, so I'm
thinking it's not that.

I'll take a look at those articles and let you know. Get some
sleep!

Thanks,
JK

Okay, it's a bit hard to tell for sure, as there seems to be another query
involved in the source, but my guess it the way Access is interpreting the
left joins. (Presumably you have already tried a compact/repair, to
eliminate the possibility of a bad index.)

IME, Access ignores the brackets in the FROM statement. This is despite the
fact that:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed) LEFT JOIN
qryFData
would give different results than:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
(We are omitting the ON clause for simplicity.)

For example, say:
- tblCommitmentsFundSource generates 1 record for ID #14492,
- tblBuggetProposed generates no record for ID #14492,
- qryFData generates 2 records for ID #14492.
Then:
(tblBuggetProposed LEFT JOIN qryFData)
would generate *no* record for ID #14492, and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate *one* record for ID #14492.

But:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed)
would geneate one record for ID #14492,
and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate 2 records for ID #14492.

So, presumably the WHERE clause is causing the query optimizer to change the
execution plan.

To be honest, I'm half asleep ATM, but if you want to investigate whether a
change of query plan really is causing the results you are seeing, these
links may help:http://msdn.microsoft.com/library/d...m/archive/default.asp?url=/archive/en-us/dnar...

If you happen to be using Access 2007, the reg setting is:
[HKLM\SOFTWARE\Microsoft\Office\12.0\Access Connectivity
Engine\Engines\Debug] "JETSHOWPLAN"="ON"

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

Allen,

(the CustomerID = 1 was a generic statement)

Here is my original query:
SELECT tblCommitmentsFundSource.*, qryFData.*
FROM (tblCommitmentsFundSource LEFT JOIN tblBudgetProposed ON
(tblCommitmentsFundSource.Description = tblBudgetProposed.Description)
AND (tblCommitmentsFundSource.BudgetItem =
tblBudgetProposed.BudgetItem) AND (tblCommitmentsFundSource.SubGroup =
tblBudgetProposed.SubGroup) AND (tblCommitmentsFundSource.Group =
tblBudgetProposed.Group) AND (tblCommitmentsFundSource.Country =
tblBudgetProposed.Country)) LEFT JOIN qryFData ON
tblBudgetProposed.ProgramSubElementID = qryFData.ProgramElementID;

This returns all records - I'm using the record with ID # 14992 as an
example. It appears in this query (and report) once.

Then, when I have this query:
SELECT tblCommitmentsFundSource.*, qryFData.*
FROM (tblCommitmentsFundSource LEFT JOIN tblBudgetProposed ON
(tblCommitmentsFundSource.Description = tblBudgetProposed.Description)
AND (tblCommitmentsFundSource.BudgetItem =
tblBudgetProposed.BudgetItem) AND (tblCommitmentsFundSource.SubGroup =
tblBudgetProposed.SubGroup) AND (tblCommitmentsFundSource.Group =
tblBudgetProposed.Group) AND (tblCommitmentsFundSource.Country =
tblBudgetProposed.Country)) LEFT JOIN qryFData ON
tblBudgetProposed.ProgramSubElementID = qryFData.ProgramElementID
WHERE (((tblCommitmentsFundSource.ObligationID)=14992));

The results show record 14992 twice. Record 14992 only appears in the
tblCommitmentsFundSource table once, and due to the Left Joins, I
don't see how it could appear twice in the results. I also can't
understand how the simple addition of a WHERE clause could cause this.

- Show quoted text -

 

[JK]

Allen,

I tried doing a number of things. I split the queries into multiple
queries, used "SELECT *" and "SELECT Field1, Field2, etc." - nothing
worked. Then the craziest thing of all; I went into the report,
opened the Record Source, and ran the query with no WHERE clause and
got one of each record as expected. Then I ran the report with no
WHERE clause and no filters - just straight-up displaying the query as
a report - and I got duplicate records. Not only that, but not all of
the records were duplicated, only some of them!!! I'm going nuts
trying to wrap my head around how this is possible.

If you have any other suggestions, I'd really appreciate it.

Oh, BTW, thanks for those articles but the computer I'm on at work
won't allow me to access the registry so I can't play around with any
keys. Maybe I'll bring it home and try it there if worse comes to
worse...

Thanks again,
JK

Allen,

I really appreciate your help on this.

Yes, I had tried a Compact/Repair, but that didn't fix it.

FYI: The query (qryFData) is simply a query that combines a few lookup
tables. tblCommitmentsFundSource has a field called
ProgramSubElementID that holds an ID value of a record in qryFData.
There is one and only one ProgramSubElementID in that query, so I'm
thinking it's not that.

I'll take a look at those articles and let you know. Get some
sleep!

Thanks,
JK

Okay, it's a bit hard to tell for sure, as there seems to be another query
involved in the source, but my guess it the way Access is interpreting the
left joins. (Presumably you have already tried a compact/repair, to
eliminate the possibility of a bad index.)

IME, Access ignores the brackets in the FROM statement. This is despite the
fact that:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed) LEFT JOIN
qryFData
would give different results than:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
(We are omitting the ON clause for simplicity.)

For example, say:
- tblCommitmentsFundSource generates 1 record for ID #14492,
- tblBuggetProposed generates no record for ID #14492,
- qryFData generates 2 records for ID #14492.
Then:
(tblBuggetProposed LEFT JOIN qryFData)
would generate *no* record for ID #14492, and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate *one* record for ID #14492.

But:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed)
would geneate one record for ID #14492,
and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate 2 records for ID #14492.

So, presumably the WHERE clause is causing the query optimizer to change the
execution plan.

To be honest, I'm half asleep ATM, but if you want to investigate whether a
change of query plan really is causing the results you are seeing, these
links may help:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnac......

If you happen to be using Access 2007, the reg setting is:
[HKLM\SOFTWARE\Microsoft\Office\12.0\Access Connectivity
Engine\Engines\Debug] "JETSHOWPLAN"="ON"

- Show quoted text -- Hide quoted text -

- Show quoted text -

 

[Allen Browne]

Did you investigate whether the order of executing of the joins was the
issue?

If it is, you can't solve that by using brackets, as JET just ignores them.
You may be able to solve it by creating a query that performs one left join,
saving it, and using it as an input "table" for the next query that performs
the final left join.

Your experience with the report still suggests the same thing. Depending on
what's in the report's Sorting'n'Grouping dialog, it alters the approach to
the query, which could alter the execution plan.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Allen,

I tried doing a number of things. I split the queries into multiple
queries, used "SELECT *" and "SELECT Field1, Field2, etc." - nothing
worked. Then the craziest thing of all; I went into the report,
opened the Record Source, and ran the query with no WHERE clause and
got one of each record as expected. Then I ran the report with no
WHERE clause and no filters - just straight-up displaying the query as
a report - and I got duplicate records. Not only that, but not all of
the records were duplicated, only some of them!!! I'm going nuts
trying to wrap my head around how this is possible.

If you have any other suggestions, I'd really appreciate it.

Oh, BTW, thanks for those articles but the computer I'm on at work
won't allow me to access the registry so I can't play around with any
keys. Maybe I'll bring it home and try it there if worse comes to
worse...

Thanks again,
JK

Allen,

I really appreciate your help on this.

Yes, I had tried a Compact/Repair, but that didn't fix it.

FYI: The query (qryFData) is simply a query that combines a few lookup
tables. tblCommitmentsFundSource has a field called
ProgramSubElementID that holds an ID value of a record in qryFData.
There is one and only one ProgramSubElementID in that query, so I'm
thinking it's not that.

I'll take a look at those articles and let you know. Get some
sleep!

Thanks,
JK

Okay, it's a bit hard to tell for sure, as there seems to be another
query
involved in the source, but my guess it the way Access is interpreting
the
left joins. (Presumably you have already tried a compact/repair, to
eliminate the possibility of a bad index.)

IME, Access ignores the brackets in the FROM statement. This is despite
the
fact that:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed) LEFT JOIN
qryFData
would give different results than:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
(We are omitting the ON clause for simplicity.)

For example, say:
- tblCommitmentsFundSource generates 1 record for ID #14492,
- tblBuggetProposed generates no record for ID #14492,
- qryFData generates 2 records for ID #14492.
Then:
(tblBuggetProposed LEFT JOIN qryFData)
would generate *no* record for ID #14492, and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate *one* record for ID #14492.

But:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed)
would geneate one record for ID #14492,
and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate 2 records for ID #14492.

So, presumably the WHERE clause is causing the query optimizer to
change the
execution plan.

To be honest, I'm half asleep ATM, but if you want to investigate
whether a
change of query plan really is causing the results you are seeing,
these
links may
help:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnac......

If you happen to be using Access 2007, the reg setting is:
[HKLM\SOFTWARE\Microsoft\Office\12.0\Access Connectivity
Engine\Engines\Debug] "JETSHOWPLAN"="ON"

(the CustomerID = 1 was a generic statement)

Here is my original query:
SELECT tblCommitmentsFundSource.*, qryFData.*
FROM (tblCommitmentsFundSource LEFT JOIN tblBudgetProposed ON
(tblCommitmentsFundSource.Description =
tblBudgetProposed.Description)
AND (tblCommitmentsFundSource.BudgetItem =
tblBudgetProposed.BudgetItem) AND (tblCommitmentsFundSource.SubGroup
=
tblBudgetProposed.SubGroup) AND (tblCommitmentsFundSource.Group =
tblBudgetProposed.Group) AND (tblCommitmentsFundSource.Country =
tblBudgetProposed.Country)) LEFT JOIN qryFData ON
tblBudgetProposed.ProgramSubElementID = qryFData.ProgramElementID;

This returns all records - I'm using the record with ID # 14992 as an
example. It appears in this query (and report) once.

Then, when I have this query:
SELECT tblCommitmentsFundSource.*, qryFData.*
FROM (tblCommitmentsFundSource LEFT JOIN tblBudgetProposed ON
(tblCommitmentsFundSource.Description =
tblBudgetProposed.Description)
AND (tblCommitmentsFundSource.BudgetItem =
tblBudgetProposed.BudgetItem) AND (tblCommitmentsFundSource.SubGroup
=
tblBudgetProposed.SubGroup) AND (tblCommitmentsFundSource.Group =
tblBudgetProposed.Group) AND (tblCommitmentsFundSource.Country =
tblBudgetProposed.Country)) LEFT JOIN qryFData ON
tblBudgetProposed.ProgramSubElementID = qryFData.ProgramElementID
WHERE (((tblCommitmentsFundSource.ObligationID)=14992));

The results show record 14992 twice. Record 14992 only appears in
the
tblCommitmentsFundSource table once, and due to the Left Joins, I
don't see how it could appear twice in the results. I also can't
understand how the simple addition of a WHERE clause could cause
this.

On Apr 18, 10:51 pm, "Allen Browne" <[email protected]>
wrote:
Post the SQL statement, including the WHERE CustomerID = 1.

I'm getting a very strange error: I have a report that is
displaying
records multiple times when I view it. When I look at the record
source of the report and run the query, I get the expected results
(listing each record once). If though, I limit the query (e.g.
WHERE
CustomerID = 1), either by using a WHERE clause in the query, or a
Filter on the report, the results show two records for CustomerID
1.
When I look in the table though, there is only one record for
CustomerID 1.

Anyone had any experience with something like this?

Any help would be greatly appreciated.

Thanks!
JK- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

 

[JK]

Allen,

After much frustration - I finally found the problem. I was wrong
earlier when I said there could not be duplicate values in the
"tblBudgetProposed" table. There was one other field that needed to
be joined between the two tables to guarentee the uniqueness and that
was missing.

I really appreciate you taking the time to work with me on this - I
wouldn't have known to look for this unless you had told me about the
different ways Access executes queries.

Thanks again,
JK

Did you investigate whether the order of executing of the joins was the
issue?

If it is, you can't solve that by using brackets, as JET just ignores them.
You may be able to solve it by creating a query that performs one left join,
saving it, and using it as an input "table" for the next query that performs
the final left join.

Your experience with the report still suggests the same thing. Depending on
what's in the report's Sorting'n'Grouping dialog, it alters the approach to
the query, which could alter the execution plan.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

Allen,

I tried doing a number of things. I split the queries into multiple
queries, used "SELECT *" and "SELECT Field1, Field2, etc." - nothing
worked. Then the craziest thing of all; I went into the report,
opened the Record Source, and ran the query with no WHERE clause and
got one of each record as expected. Then I ran the report with no
WHERE clause and no filters - just straight-up displaying the query as
a report - and I got duplicate records. Not only that, but not all of
the records were duplicated, only some of them!!! I'm going nuts
trying to wrap my head around how this is possible.

If you have any other suggestions, I'd really appreciate it.

Oh, BTW, thanks for those articles but the computer I'm on at work
won't allow me to access the registry so I can't play around with any
keys. Maybe I'll bring it home and try it there if worse comes to
worse...

Thanks again,
JK

Allen,
I really appreciate your help on this.
Yes, I had tried a Compact/Repair, but that didn't fix it.
FYI: The query (qryFData) is simply a query that combines a few lookup
tables. tblCommitmentsFundSource has a field called
ProgramSubElementID that holds an ID value of a record in qryFData.
There is one and only one ProgramSubElementID in that query, so I'm
thinking it's not that.
I'll take a look at those articles and let you know. Get some
sleep!
Thanks,
JK
Okay, it's a bit hard to tell for sure, as there seems to be another
query
involved in the source, but my guess it the way Access is interpreting
the
left joins. (Presumably you have already tried a compact/repair, to
eliminate the possibility of a bad index.)
IME, Access ignores the brackets in the FROM statement. This is despite
the
fact that:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed) LEFT JOIN
qryFData
would give different results than:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
(We are omitting the ON clause for simplicity.)
For example, say:
- tblCommitmentsFundSource generates 1 record for ID #14492,
- tblBuggetProposed generates no record for ID #14492,
- qryFData generates 2 records for ID #14492.
Then:
(tblBuggetProposed LEFT JOIN qryFData)
would generate *no* record for ID #14492, and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate *one* record for ID #14492.
But:
(tblCommitmentsFundSource LEFT JOIN tblBuggetProposed)
would geneate one record for ID #14492,
and so:
tblCommitmentsFundSource LEFT JOIN (tblBuggetProposed LEFT JOIN
qryFData)
would generate 2 records for ID #14492.
So, presumably the WHERE clause is causing the query optimizer to
change the
execution plan.
To be honest, I'm half asleep ATM, but if you want to investigate
whether a
change of query plan really is causing the results you are seeing,
these
links may
help:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnac......
If you happen to be using Access 2007, the reg setting is:
[HKLM\SOFTWARE\Microsoft\Office\12.0\Access Connectivity
Engine\Engines\Debug] "JETSHOWPLAN"="ON"
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

Allen,
(the CustomerID = 1 was a generic statement)
Here is my original query:
SELECT tblCommitmentsFundSource.*, qryFData.*
FROM (tblCommitmentsFundSource LEFT JOIN tblBudgetProposed ON
(tblCommitmentsFundSource.Description =
tblBudgetProposed.Description)
AND (tblCommitmentsFundSource.BudgetItem =
tblBudgetProposed.BudgetItem) AND (tblCommitmentsFundSource.SubGroup
=
tblBudgetProposed.SubGroup) AND (tblCommitmentsFundSource.Group =
tblBudgetProposed.Group) AND (tblCommitmentsFundSource.Country =
tblBudgetProposed.Country)) LEFT JOIN qryFData ON
tblBudgetProposed.ProgramSubElementID = qryFData.ProgramElementID;
This returns all records - I'm using the record with ID # 14992 as an
example. It appears in this query (and report) once.
Then, when I have this query:
SELECT tblCommitmentsFundSource.*, qryFData.*
FROM (tblCommitmentsFundSource LEFT JOIN tblBudgetProposed ON
(tblCommitmentsFundSource.Description =
tblBudgetProposed.Description)
AND (tblCommitmentsFundSource.BudgetItem =
tblBudgetProposed.BudgetItem) AND (tblCommitmentsFundSource.SubGroup
=
tblBudgetProposed.SubGroup) AND (tblCommitmentsFundSource.Group =
tblBudgetProposed.Group) AND (tblCommitmentsFundSource.Country =
tblBudgetProposed.Country)) LEFT JOIN qryFData ON
tblBudgetProposed.ProgramSubElementID = qryFData.ProgramElementID
WHERE (((tblCommitmentsFundSource.ObligationID)=14992));
The results show record 14992 twice. Record 14992 only appears in
the
tblCommitmentsFundSource table once, and due to the Left Joins, I
don't see how it could appear twice in the results. I also can't
understand how the simple addition of a WHERE clause could cause
this.
On Apr 18, 10:51 pm, "Allen Browne" <[email protected]>
wrote:
Post the SQL statement, including the WHERE CustomerID = 1.

I'm getting a very strange error: I have a report that is
displaying
records multiple times when I view it. When I look at the record
source of the report and run the query, I get the expected results
(listing each record once). If though, I limit the query (e.g.
WHERE
CustomerID = 1), either by using a WHERE clause in the query, or a
Filter on the report, the results show two records for CustomerID
1.
When I look in the table though, there is only one record for
CustomerID 1.
Anyone had any experience with something like this?
Any help would be greatly appreciated.
Thanks!
JK- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -- Hide quoted text -

- Show quoted text -