S
straits58 via AccessMonster.com
I am a self-taught newbie on Access with no programming experience, so
forgive me if my post uses incorrect language.
My company produces electronic catalogs for manufacturing clients. Some of
those manufacturers have two versions of their catalogs, one that is fully
populated with all their graphics and data, and another that matches it
except that it isn't populated with the graphics. This second version we call
a 'shared dependency' catalog because it depends on the first version to
'pull' graphics from.
I access (pun intended) a company database that has been designed, created
and is maintained by others for storing the information about these catalogs.
So far I have figured out how to create my own queries and reports to extract
information I need for my work except for one thing. There is a
DependentCatalog field in the Catalogs table that contains a value for the
Shared Dependency (SD) catalogs. This value is the three character catalog
code of the full catalog that the SD catalog depends on. For instance, let's
say manufacturer A has two catalogs, CA1 and CA2, and CA2 is dependent on CA1.
These CA1 and CA2 catalogs are each entered as their own record in the
CatalogCode field of the Catalogs table, and in the DependentCatalog field
for the CA2 record you would find the code CA1. The CatalogCode field is a
unique value, and therefore is used as the Primary Key in the Catalogs table
(and is one half of a one to many relationship with a Manufacturers table).
The DependentCatalog field is set up as a Number Data type, Long Integer
Field Size, ComboBox that references the PK CatalogID field (Bound Column 1)
of the same Catalogs table that the DependentCatalog field is in, and is set
to display the CatalogCode field (Column Count 2) of that table. The
CatalogCode field that the DependentCatalog field depends on has historically
only had 3 characters in it, no more and no less. However, a new naming
convention is on the horizon and this fixed character length may go out the
window to be replaced with a variable length string.
I run a report that lists all of the catalogs that have been released for
production, and I need to 'mark' those that are Shared Dependency, among
several other things that get 'marked' for these catalogs. These 'marks' take
the form of a large bullet character in a Text Box in a column of the report.
What I cannot figure out how to do is have the report look to see if the
DependentCatalog field for a catalog record is populated, and then to insert
the special bullet character into the SD column of those that are.
I have searched and searched these forums for a solution, but I must not be
using the correct search terms because I haven't come up with a solution that
has worked yet. I can get a subset of the total number of catalogs to get
'bulleted' with various code examples, but those bullets don't correspond to
whether or not the DependentCatalog field is populated. I don't know how the
heck it happens, but the incorrect attempts seem to be evaluating something
other than the visible content of the DependentCatalog field.
One of the incorrect code attempts:
=IIf(IsNull([DependentCatalog]),"","l")
entered into the Control Source field of the Text Box Properties using the
Expression Builder.
Any help would be GREATLY appreciated.
Steve
forgive me if my post uses incorrect language.
My company produces electronic catalogs for manufacturing clients. Some of
those manufacturers have two versions of their catalogs, one that is fully
populated with all their graphics and data, and another that matches it
except that it isn't populated with the graphics. This second version we call
a 'shared dependency' catalog because it depends on the first version to
'pull' graphics from.
I access (pun intended) a company database that has been designed, created
and is maintained by others for storing the information about these catalogs.
So far I have figured out how to create my own queries and reports to extract
information I need for my work except for one thing. There is a
DependentCatalog field in the Catalogs table that contains a value for the
Shared Dependency (SD) catalogs. This value is the three character catalog
code of the full catalog that the SD catalog depends on. For instance, let's
say manufacturer A has two catalogs, CA1 and CA2, and CA2 is dependent on CA1.
These CA1 and CA2 catalogs are each entered as their own record in the
CatalogCode field of the Catalogs table, and in the DependentCatalog field
for the CA2 record you would find the code CA1. The CatalogCode field is a
unique value, and therefore is used as the Primary Key in the Catalogs table
(and is one half of a one to many relationship with a Manufacturers table).
The DependentCatalog field is set up as a Number Data type, Long Integer
Field Size, ComboBox that references the PK CatalogID field (Bound Column 1)
of the same Catalogs table that the DependentCatalog field is in, and is set
to display the CatalogCode field (Column Count 2) of that table. The
CatalogCode field that the DependentCatalog field depends on has historically
only had 3 characters in it, no more and no less. However, a new naming
convention is on the horizon and this fixed character length may go out the
window to be replaced with a variable length string.
I run a report that lists all of the catalogs that have been released for
production, and I need to 'mark' those that are Shared Dependency, among
several other things that get 'marked' for these catalogs. These 'marks' take
the form of a large bullet character in a Text Box in a column of the report.
What I cannot figure out how to do is have the report look to see if the
DependentCatalog field for a catalog record is populated, and then to insert
the special bullet character into the SD column of those that are.
I have searched and searched these forums for a solution, but I must not be
using the correct search terms because I haven't come up with a solution that
has worked yet. I can get a subset of the total number of catalogs to get
'bulleted' with various code examples, but those bullets don't correspond to
whether or not the DependentCatalog field is populated. I don't know how the
heck it happens, but the incorrect attempts seem to be evaluating something
other than the visible content of the DependentCatalog field.
One of the incorrect code attempts:
=IIf(IsNull([DependentCatalog]),"","l")
entered into the Control Source field of the Text Box Properties using the
Expression Builder.
Any help would be GREATLY appreciated.
Steve