Populate Text Box

[Guest]

I've tried posting this a couple times now and I think my attempts were less
than clear which resulted in some very nice efforts to resolve but ultimately
I'm back out in left field.

I think I've found a clearer way to present the problem.

I have a report that queries:
tblProfiles.txtProfileID

This is sourced by 2 text boxes:
txtProfileID
RDIngPKID

The report also queries:
tblProfiles.Description

This is sourced by 2 text boxes:
Description
RDIngPKIDDescription

The result is a report with 4 text boxes:
txtProfileID > Description
RDIngPKID > RDIngPKIDDescription

txtProfileID is Master Link for the entire report so its Description field
displays accordingly.

My problem is getting RDIngPKIDDescription to display according to the value
in RDIngPKID.

How can I resolve this?

Thanks for your help!

 

[Duane Hookom]

You have only mentioned one table when I expect this issue involves more
than one table. "This is sourced by 2 text boxes" doesn't make make sense.
What is "sourced" and where are the 2 text boxes coming from?

Are there lookup fields in your tables?

What is the record source of your report?

Can you provide some table and field names?

 

[Guest]

Hi, Duane.

LOL! So much for what I thought was a clearer presentation!

You have only mentioned one table when I expect this issue involves more
than one table.

Yes. The report involves more than one table (see record source below).

"This is sourced by 2 text boxes" doesn't make make sense.
What is "sourced" and where are the 2 text boxes coming from?

Both txtProfileID and RDIngPKID source (Row Source) tblProfiles.txtProfileID
in the form. In the report they are coming from:
tblProfiles.txtProfileID
tblProfilesRevisions.RDIngPKID

Are there lookup fields in your tables?
No.


What is the record source of your report?

It's big:
SELECT tblProfilesRevisions.numProfilesRevisionsID,
tblProfilesRevisions.txtProfileID, tblProfilesRevisions.InitiationDate,
tblProfilesRevisions.Initiators, tblProfilesRevisions.SpecType,
tblProfilesRevisions.STComments, tblProfilesRevisions.RevisionType,
tblProfilesRevisions.EffectiveDate, tblProfilesRevisions.EffDateComments,
tblProfilesRevisions.EndingDate, tblProfilesRevisions.EndDateComments,
tblProfilesRevisions.RDIngPKID, tblProfilesRevisions.PrevRDIngPKID,
tblProfilesRevisions.Revision, tblProfilesRevisions.FoodConsumerSafety,
tblProfilesRevisions.Quality, tblProfilesRevisions.Productivity,
tblProfilesRevisions.Cost, tblProfilesRevisions.CustomerRequest,
tblProfilesRevisions.Other, tblProfilesRevisions.Reason,
tblProfilesRevisions.Justification, tblProfilesRevisions.OtherInformation,
tblProfilesRevisions.KosherStatus, tblProfilesRevisions.KSComments,
tblProfilesRevisions.LabelStatus, tblProfilesRevisions.LSComments,
tblProfilesRevisions.CustomerApproval, tblProfilesRevisions.CAComments,
tblProfilesRevisions.[02NewYorkFrozenFoods],
tblProfilesRevisions.[05W1MZFrozenPasta], tblProfilesRevisions.[53InnMaid],
tblProfilesRevisions.C1ChathamVillage, tblProfilesRevisions.CoPacker,
tblProfilesRevisions.DressingsDips, tblProfilesRevisions.L1MammaBella,
tblProfilesRevisions.Marketing, tblProfilesRevisions.RDFoodservice,
tblProfilesRevisions.RDRetail, tblProfilesRevisions.S3SisterSchuberts,
tblProfilesRevisions.Sales, tblProfilesRevisions.DistributionComments,
tblProfilesRevisions.Status, tblProfilesRevisions.StatusComments,
tblProfilesRevisions.IssueNumber, tblProfilesRevisions.PublishDate,
tblProfiles.Description
FROM tblProfiles INNER JOIN tblProfilesRevisions ON tblProfiles.txtProfileID
= tblProfilesRevisions.txtProfileID;

 

[Duane Hookom]

What table does RDIngPKIDDescription come from? If it comes from
tblProfiles, you need to add tblProfiles (a second time) into your report's
recordsource.

--
Duane Hookom
MS Access MVP

Hi, Duane.

LOL! So much for what I thought was a clearer presentation!

You have only mentioned one table when I expect this issue involves more
than one table.

Yes. The report involves more than one table (see record source below).

"This is sourced by 2 text boxes" doesn't make make sense.
What is "sourced" and where are the 2 text boxes coming from?

Both txtProfileID and RDIngPKID source (Row Source)
tblProfiles.txtProfileID
in the form. In the report they are coming from:
tblProfiles.txtProfileID
tblProfilesRevisions.RDIngPKID

Are there lookup fields in your tables?
No.


What is the record source of your report?

It's big:
SELECT tblProfilesRevisions.numProfilesRevisionsID,
tblProfilesRevisions.txtProfileID, tblProfilesRevisions.InitiationDate,
tblProfilesRevisions.Initiators, tblProfilesRevisions.SpecType,
tblProfilesRevisions.STComments, tblProfilesRevisions.RevisionType,
tblProfilesRevisions.EffectiveDate, tblProfilesRevisions.EffDateComments,
tblProfilesRevisions.EndingDate, tblProfilesRevisions.EndDateComments,
tblProfilesRevisions.RDIngPKID, tblProfilesRevisions.PrevRDIngPKID,
tblProfilesRevisions.Revision, tblProfilesRevisions.FoodConsumerSafety,
tblProfilesRevisions.Quality, tblProfilesRevisions.Productivity,
tblProfilesRevisions.Cost, tblProfilesRevisions.CustomerRequest,
tblProfilesRevisions.Other, tblProfilesRevisions.Reason,
tblProfilesRevisions.Justification, tblProfilesRevisions.OtherInformation,
tblProfilesRevisions.KosherStatus, tblProfilesRevisions.KSComments,
tblProfilesRevisions.LabelStatus, tblProfilesRevisions.LSComments,
tblProfilesRevisions.CustomerApproval, tblProfilesRevisions.CAComments,
tblProfilesRevisions.[02NewYorkFrozenFoods],
tblProfilesRevisions.[05W1MZFrozenPasta],
tblProfilesRevisions.[53InnMaid],
tblProfilesRevisions.C1ChathamVillage, tblProfilesRevisions.CoPacker,
tblProfilesRevisions.DressingsDips, tblProfilesRevisions.L1MammaBella,
tblProfilesRevisions.Marketing, tblProfilesRevisions.RDFoodservice,
tblProfilesRevisions.RDRetail, tblProfilesRevisions.S3SisterSchuberts,
tblProfilesRevisions.Sales, tblProfilesRevisions.DistributionComments,
tblProfilesRevisions.Status, tblProfilesRevisions.StatusComments,
tblProfilesRevisions.IssueNumber, tblProfilesRevisions.PublishDate,
tblProfiles.Description
FROM tblProfiles INNER JOIN tblProfilesRevisions ON
tblProfiles.txtProfileID
= tblProfilesRevisions.txtProfileID;

 

[Guest]

What table does RDIngPKIDDescription come from? If it comes from

tblProfiles, you need to add tblProfiles (a second time) into your report's
recordsource.

It doesn't come from anywhere specifically as it's not a saved value. In the
form I use this for its Control Source:
=[RDIngPKID].[Column](1)

This works fine. I'm trying to accomplish the same with the report.

 

[Duane Hookom]

Now, you are really confusing me with "It doesn't come from anywhere
specifically". The description must be stored somewhere in your database.
Apparently you are using a combo box somewhere. How about providing the Row
Source property of the combo box?

--
Duane Hookom
MS Access MVP

What table does RDIngPKIDDescription come from? If it comes from
tblProfiles, you need to add tblProfiles (a second time) into your
report's
recordsource.

It doesn't come from anywhere specifically as it's not a saved value. In
the
form I use this for its Control Source:
=[RDIngPKID].[Column](1)

This works fine. I'm trying to accomplish the same with the report.

 

[Guest]

Sorry! I greatly appreciate your trying to understand!

In the form the text box RDIngPKIDDescription is UNBOUND. It's Control
Source of =[RDIngPKID].[Column](1) populates it when a record is selected for
RDIngPKID.

Therefore I'm trying to get the text box RDIngPKIDDescription (also unbound)
in the report to populate according to the value from
tblProfilesRevisions.RDIngPKIDDescription.

I hope I haven't muddied the waters further!

--
www.Marzetti.com

Now, you are really confusing me with "It doesn't come from anywhere
specifically". The description must be stored somewhere in your database.
Apparently you are using a combo box somewhere. How about providing the Row
Source property of the combo box?

--
Duane Hookom
MS Access MVP

What table does RDIngPKIDDescription come from? If it comes from
tblProfiles, you need to add tblProfiles (a second time) into your
report's
recordsource.

It doesn't come from anywhere specifically as it's not a saved value. In
the
form I use this for its Control Source:
=[RDIngPKID].[Column](1)

This works fine. I'm trying to accomplish the same with the report.

 

[Guest]

Your control [RDIngPKID] is a list box or a combo box that has a recordsource.
What is being used to populate this control? You must have have a query that
returns at least 2 columns... you are grabbing the second value to populate
RDIngPKIDDescription when a record is selected for RDIngPKID.

The simplest thing for you to do is have the form open when you call your
report. Then you can just assign the value in your report to the value
already established on your form.

Hope this helps...

 

[Duane Hookom]

Thanks JoyAA. All we should need to ascertain is the Row Source property of
RDIngPKID. I expect this is based on a table that should be included in your
report's recordsource.

 

[Guest]

The Row Source is:
SELECT tblProfiles.txtProfileID, tblProfiles.Description, tblProfiles.Type
FROM tblProfiles ORDER BY tblProfiles.txtProfileID, tblProfiles.Type;

--
www.Marzetti.com

Thanks JoyAA. All we should need to ascertain is the Row Source property of
RDIngPKID. I expect this is based on a table that should be included in your
report's recordsource.

--
Duane Hookom
MS Access MVP

Your control [RDIngPKID] is a list box or a combo box that has a
recordsource.
What is being used to populate this control? You must have have a query
that
returns at least 2 columns... you are grabbing the second value to
populate
RDIngPKIDDescription when a record is selected for RDIngPKID.

The simplest thing for you to do is have the form open when you call your
report. Then you can just assign the value in your report to the value
already established on your form.

Hope this helps...

 

[Guest]

Can't you just add tblProfiles to your report's recordsource (if it is
already there, add it again) and join the txtProfileID fields/columns. Add
the tblProfiles.Description to the record source fields. If you have another
field in the grid named "Description", then change the name of this column.

--
Duane Hookom
Microsoft Access MVP

The Row Source is:
SELECT tblProfiles.txtProfileID, tblProfiles.Description, tblProfiles.Type
FROM tblProfiles ORDER BY tblProfiles.txtProfileID, tblProfiles.Type;

--
www.Marzetti.com

Thanks JoyAA. All we should need to ascertain is the Row Source property of
RDIngPKID. I expect this is based on a table that should be included in your
report's recordsource.

--
Duane Hookom
MS Access MVP

Your control [RDIngPKID] is a list box or a combo box that has a
recordsource.
What is being used to populate this control? You must have have a query
that
returns at least 2 columns... you are grabbing the second value to
populate
RDIngPKIDDescription when a record is selected for RDIngPKID.

The simplest thing for you to do is have the form open when you call your
report. Then you can just assign the value in your report to the value
already established on your form.

Hope this helps...

 

[Guest]

Thanks, Duane.

I just gave that a try. No good.

I think Joy's answer is the way to go but I'm having trouble setting up the
DLookUp. in my other thread regarding this same problem:

Thanks, Willem.

I've posted this problem several times and can't seem to work it out. Simply
put:

The field [tblProfiles].[Description] is used for two text boxes. One of the
boxes is bound to [tblProfiles].[Description] and the other is unbound and
needs to display [tblProfiles].[Description] according to the value in
[tblProfilesRevisions].[RDIngPackID]. This value comes from
[tblProfiles].[txtProfileID] as it's a combo box in the firm with the Row
Source of SELECT tblProfiles.txtProfileID, tblProfiles.Description,
tblProfiles.Type FROM tblProfiles ORDER BY tblProfiles.txtProfileID,
tblProfiles.Type;. Therefore, I had to rename the field to [RDIngPackID].

The reason for this design is complicated and will only serve to muddy the
waters if I draw it all out.

I hope that makes sense!

--
www.Marzetti.com

I am getting a bit confused with all the names you use, but you could
try this:
=DLookUp("[Description]","tblProfiles", "[RDIngPKIDDescription ] = " &
[RDIngPKID])

You might have to use a semicolon ( as a seperator instead of a
comma.
=DLookUp("[Description]";"tblProfiles"; "[RDIngPKIDDescription ] = " &
[RDIngPKID])

--
www.Marzetti.com

Can't you just add tblProfiles to your report's recordsource (if it is
already there, add it again) and join the txtProfileID fields/columns. Add
the tblProfiles.Description to the record source fields. If you have another
field in the grid named "Description", then change the name of this column.

--
Duane Hookom
Microsoft Access MVP

The Row Source is:
SELECT tblProfiles.txtProfileID, tblProfiles.Description, tblProfiles.Type
FROM tblProfiles ORDER BY tblProfiles.txtProfileID, tblProfiles.Type;

--
www.Marzetti.com

Thanks JoyAA. All we should need to ascertain is the Row Source property of
RDIngPKID. I expect this is based on a table that should be included in your
report's recordsource.

--
Duane Hookom
MS Access MVP

Your control [RDIngPKID] is a list box or a combo box that has a
recordsource.
What is being used to populate this control? You must have have a query
that
returns at least 2 columns... you are grabbing the second value to
populate
RDIngPKIDDescription when a record is selected for RDIngPKID.

The simplest thing for you to do is have the form open when you call your
report. Then you can just assign the value in your report to the value
already established on your form.

Hope this helps...

 

[Guest]

It sounds like you have two fields in TableA that contain values that are
used to lookup description field values in two different records in TableB.
If that is the case, you can add TableB twice into a query with TableA and
join each of the two fields in TableA with the primary key value in a copy of
TableB.

--
Duane Hookom
Microsoft Access MVP

Thanks, Duane.

I just gave that a try. No good.

I think Joy's answer is the way to go but I'm having trouble setting up the
DLookUp. in my other thread regarding this same problem:

Thanks, Willem.

I've posted this problem several times and can't seem to work it out. Simply
put:

The field [tblProfiles].[Description] is used for two text boxes. One of the
boxes is bound to [tblProfiles].[Description] and the other is unbound and
needs to display [tblProfiles].[Description] according to the value in
[tblProfilesRevisions].[RDIngPackID]. This value comes from
[tblProfiles].[txtProfileID] as it's a combo box in the firm with the Row
Source of SELECT tblProfiles.txtProfileID, tblProfiles.Description,
tblProfiles.Type FROM tblProfiles ORDER BY tblProfiles.txtProfileID,
tblProfiles.Type;. Therefore, I had to rename the field to [RDIngPackID].

The reason for this design is complicated and will only serve to muddy the
waters if I draw it all out.

I hope that makes sense!

--
www.Marzetti.com

I am getting a bit confused with all the names you use, but you could
try this:
=DLookUp("[Description]","tblProfiles", "[RDIngPKIDDescription ] = " &
[RDIngPKID])

You might have to use a semicolon ( as a seperator instead of a
comma.
=DLookUp("[Description]";"tblProfiles"; "[RDIngPKIDDescription ] = " &
[RDIngPKID])

--
www.Marzetti.com

Can't you just add tblProfiles to your report's recordsource (if it is
already there, add it again) and join the txtProfileID fields/columns. Add
the tblProfiles.Description to the record source fields. If you have another
field in the grid named "Description", then change the name of this column.

--
Duane Hookom
Microsoft Access MVP

The Row Source is:
SELECT tblProfiles.txtProfileID, tblProfiles.Description, tblProfiles.Type
FROM tblProfiles ORDER BY tblProfiles.txtProfileID, tblProfiles.Type;

--
www.Marzetti.com


:

Thanks JoyAA. All we should need to ascertain is the Row Source property of
RDIngPKID. I expect this is based on a table that should be included in your
report's recordsource.

--
Duane Hookom
MS Access MVP

Your control [RDIngPKID] is a list box or a combo box that has a
recordsource.
What is being used to populate this control? You must have have a query
that
returns at least 2 columns... you are grabbing the second value to
populate
RDIngPKIDDescription when a record is selected for RDIngPKID.

The simplest thing for you to do is have the form open when you call your
report. Then you can just assign the value in your report to the value
already established on your form.

Hope this helps...

 

[Guest]

Hey, Duane.

You're starting to get it! I'm beginning to see a light at the end of the
tunnel!

It sounds like you have two fields in TableA that contain values that are
used to lookup description field values in two different records in TableB.
If that is the case, you can add TableB twice into a query with TableA and
join each of the two fields in TableA with the primary key value in a copy of
TableB.

Not quite.

I have one field in TableA that is bound to one text box in the report and
unbound to another.

 

[Duane Hookom]

To be clear, you have only one table containing any significant values in
your issue?
To me, an unbound control has absolutely no control source value. Is this
situation?

 

[Guest]

To be clear, you have only one table containing any significant values in

your issue?

Yes. tblProfilesRevisions contains RDIngPKID. This field is a combo box with
tblProfiles.txtProfileID in its Row Source. tblProfilesRevisions houses many
revisions to one txtProfileID.

tblProfiles also contains the field Description. The PK for tblProfiles is
txtProfileID. Example:
txtProfileID Description
12345 CANDY CORN

To me, an unbound control has absolutely no control source value. Is this
situation?

Yes again! The text box RDIngPKIDDescription is unbound BUT needs values
from tblProfiles.Description accordingly. So a record in tblProfilesRevisions
will be recorded:
RDIngPKID
12345

RDIngPKIDDescription is unbound. I can make it appear in the form with the
Control Source:
=[RDIngPKID].[Column](1)

The problem is making it appear in the report.

I recognize the odd design here but without clouding the issue further all I
can say is that it's entirely necessary.

Thanks for taking the time to sort this out!

 

[Guest]

It is still not clear to me why you don't add [tblProfiles] to your report's
record source and join the [RDIngPKID] from your existing table to
[tblProfiles].[txtProfileID] and the drop the [Description] into the query
grid so that it is available in the report.

--
Duane Hookom
Microsoft Access MVP

To be clear, you have only one table containing any significant values in
your issue?

Yes. tblProfilesRevisions contains RDIngPKID. This field is a combo box with
tblProfiles.txtProfileID in its Row Source. tblProfilesRevisions houses many
revisions to one txtProfileID.

tblProfiles also contains the field Description. The PK for tblProfiles is
txtProfileID. Example:
txtProfileID Description
12345 CANDY CORN

To me, an unbound control has absolutely no control source value. Is this
situation?

Yes again! The text box RDIngPKIDDescription is unbound BUT needs values
from tblProfiles.Description accordingly. So a record in tblProfilesRevisions
will be recorded:
RDIngPKID
12345

RDIngPKIDDescription is unbound. I can make it appear in the form with the
Control Source:
=[RDIngPKID].[Column](1)

The problem is making it appear in the report.

I recognize the odd design here but without clouding the issue further all I
can say is that it's entirely necessary.

Thanks for taking the time to sort this out!

 

[Guest]

I've tried that per your previous suggestion:

SELECT tblProfiles.*, tblProfilesRevisions.*, tblProfiles_1.Description FROM
tblProfiles INNER JOIN (tblProfilesRevisions INNER JOIN tblProfiles AS
tblProfiles_1 ON tblProfilesRevisions.RDIngPKID = tblProfiles_1.txtProfileID)
ON tblProfiles.txtProfileID = tblProfilesRevisions.txtProfileID;

This results in:
"The specified field 'Description' could refer to more than one table listed
in the FROM clause of your SQL statement."

So does this:
SELECT tblProfiles.txtProfileID, tblProfiles.Version, tblProfiles.Type,
tblProfiles.Description, tblProfilesRevisions.*, tblProfiles_1.Description,
tblProfiles.OriginDate, tblProfiles.ApprovedDate, tblProfiles.ActiveDate,
tblProfiles.Activity, tblProfiles.InactiveDate, tblProfiles.Comments
FROM tblProfiles INNER JOIN (tblProfilesRevisions INNER JOIN tblProfiles AS
tblProfiles_1 ON tblProfilesRevisions.RDIngPKID = tblProfiles_1.txtProfileID)
ON tblProfiles.txtProfileID = tblProfilesRevisions.txtProfileID;

What am I missing...?

--
www.Marzetti.com

It is still not clear to me why you don't add [tblProfiles] to your report's
record source and join the [RDIngPKID] from your existing table to
[tblProfiles].[txtProfileID] and the drop the [Description] into the query
grid so that it is available in the report.

--
Duane Hookom
Microsoft Access MVP

To be clear, you have only one table containing any significant values in
your issue?

Yes. tblProfilesRevisions contains RDIngPKID. This field is a combo box with
tblProfiles.txtProfileID in its Row Source. tblProfilesRevisions houses many
revisions to one txtProfileID.

tblProfiles also contains the field Description. The PK for tblProfiles is
txtProfileID. Example:
txtProfileID Description
12345 CANDY CORN

To me, an unbound control has absolutely no control source value. Is this
situation?

Yes again! The text box RDIngPKIDDescription is unbound BUT needs values
from tblProfiles.Description accordingly. So a record in tblProfilesRevisions
will be recorded:
RDIngPKID
12345

RDIngPKIDDescription is unbound. I can make it appear in the form with the
Control Source:
=[RDIngPKID].[Column](1)

The problem is making it appear in the report.

I recognize the odd design here but without clouding the issue further all I
can say is that it's entirely necessary.

Thanks for taking the time to sort this out!

 

[Guest]

I replied several messages back that if the Description field is in the query
more than once, rename it.
<Quote>If you have another field in the grid named "Description", then
change the name of this column.</Quote>

SELECT tblProfiles.*, tblProfilesRevisions.*, tblProfiles_1.Description As
NudderDescription
FROM tblProfiles INNER JOIN (tblProfilesRevisions INNER JOIN tblProfiles AS
tblProfiles_1 ON tblProfilesRevisions.RDIngPKID = tblProfiles_1.txtProfileID)
ON tblProfiles.txtProfileID = tblProfilesRevisions.txtProfileID;
--
Duane Hookom
Microsoft Access MVP

I've tried that per your previous suggestion:

SELECT tblProfiles.*, tblProfilesRevisions.*, tblProfiles_1.Description FROM
tblProfiles INNER JOIN (tblProfilesRevisions INNER JOIN tblProfiles AS
tblProfiles_1 ON tblProfilesRevisions.RDIngPKID = tblProfiles_1.txtProfileID)
ON tblProfiles.txtProfileID = tblProfilesRevisions.txtProfileID;

This results in:
"The specified field 'Description' could refer to more than one table listed
in the FROM clause of your SQL statement."

So does this:
SELECT tblProfiles.txtProfileID, tblProfiles.Version, tblProfiles.Type,
tblProfiles.Description, tblProfilesRevisions.*, tblProfiles_1.Description,
tblProfiles.OriginDate, tblProfiles.ApprovedDate, tblProfiles.ActiveDate,
tblProfiles.Activity, tblProfiles.InactiveDate, tblProfiles.Comments
FROM tblProfiles INNER JOIN (tblProfilesRevisions INNER JOIN tblProfiles AS
tblProfiles_1 ON tblProfilesRevisions.RDIngPKID = tblProfiles_1.txtProfileID)
ON tblProfiles.txtProfileID = tblProfilesRevisions.txtProfileID;

What am I missing...?

--
www.Marzetti.com

It is still not clear to me why you don't add [tblProfiles] to your report's
record source and join the [RDIngPKID] from your existing table to
[tblProfiles].[txtProfileID] and the drop the [Description] into the query
grid so that it is available in the report.

--
Duane Hookom
Microsoft Access MVP

To be clear, you have only one table containing any significant values in
your issue?

Yes. tblProfilesRevisions contains RDIngPKID. This field is a combo box with
tblProfiles.txtProfileID in its Row Source. tblProfilesRevisions houses many
revisions to one txtProfileID.

tblProfiles also contains the field Description. The PK for tblProfiles is
txtProfileID. Example:
txtProfileID Description
12345 CANDY CORN

To me, an unbound control has absolutely no control source value. Is this
situation?

Yes again! The text box RDIngPKIDDescription is unbound BUT needs values
from tblProfiles.Description accordingly. So a record in tblProfilesRevisions
will be recorded:
RDIngPKID
12345

RDIngPKIDDescription is unbound. I can make it appear in the form with the
Control Source:
=[RDIngPKID].[Column](1)

The problem is making it appear in the report.

I recognize the odd design here but without clouding the issue further all I
can say is that it's entirely necessary.

Thanks for taking the time to sort this out!

 

[Guest]

Duane:

I replied several messages back that if the Description field is in the query
more than once, rename it.

You know I tried that but it didn't work so I figured either I did something
wrong or maybe it wasn't the best solution.

I've corrected my error and things work! FYI I actually presented only 1/2
of the problem here. There's really 3 text boxes that reference Description.
I only listed the 2 previously as I figured whatever solution there was could
be applied to the 3rd box. I thought bringing the 3rd box into the picture
would only confound an already screwy situation further:

SELECT tblProfiles.*, tblProfilesRevisions.*, tblProfiles_1.Description AS
RDIngPKIDDescription, tblProfiles_2.Description AS PrevRDIngPKIDDescription
FROM (tblProfiles INNER JOIN (tblProfilesRevisions INNER JOIN tblProfiles AS
tblProfiles_1 ON tblProfilesRevisions.RDIngPKID = tblProfiles_1.txtProfileID)
ON tblProfiles.txtProfileID = tblProfilesRevisions.txtProfileID) INNER JOIN
tblProfiles AS tblProfiles_2 ON tblProfilesRevisions.PrevRDIngPKID =
tblProfiles_2.txtProfileID;

I can't thank you enough for helping to resolve this!!! As yo uknow I've
posted this several times and have gotten several possible solutions but this
is the simplest and most logical - and it WORKS. I had the sense that you
didn't care for the multiple postings BUT in this instance it paid off. Too
many times I've posted something and seen other posts that were answered but
not RESOLVED. I REALLY needed to resolve this one so again, I appreciate your
persistence!

Have a great holiday!