URGENT! Current() function

[Scott L. Heim [MSFT]]

Hi Adam,

Can you provide me with the data structure that your InfoPath form is based
on as well as the secondary data sources for the drop-down lists?

In other words, document for me the bare minimum steps I would need to
reproduce a sample form that works like yours.

Scott L. Heim
Microsoft Developer Support

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

 

[Adam Harding]

Main Conection in Access is setup with all one-to-many relationships

Users_by_Info TABLE
Title
Name
Employment No(Key Field)
Cost Centre
Cost Centre Description
Job Title
Category_Level TABLE
Category
Employee Number
Competency Number
Competency_Level TABLE
Competenecy_Numbers
Skill_Number
Sub-Sub_Category

Skills_by_User TABLE

Skill_Numbers

Skill

ID
3 secondary data sources

d:Category_for_Job_Skills
@Category
@Category Number

d:Category-Sub_for_Job_Skills
@Category
@Competency
@Category Numbers

d:Category-Sub-Sub_for_Job_Skills
@Category
@Competency
@Skills
@KeyField

Form problems is with 3 DD boxes forming a cascading list from Category
through Competency onto Skill.

I that what you wanted?

 

[Scott L. Heim [MSFT]]

Hi Adam,

Thanks. You documented the primary key field for the Users_By_Info table -
what are the primary key fields for the other tables? Do you have
relationships created in Access for these tables? If so, what fields are
each of these tables related on?

For instance, in looking at what you provided it appears as though these
should be as follows:

Users_By_Info --> Category_Level (1 --> Many)
Competency_Level --> Category_Level (1 --> Many)

So basically the Category_Level table is a "join" table between the other
two - is this correct?

Either way, please confirm the primary key fields and how these should be
related.

Thanks!

Scott L. Heim
Microsoft Developer Support

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

 

[Adam Harding]

Yep

In Category Level Primary Key is Competency Number to give a 1-2-many with
Competency Level, which in turn has a 1-2-many with Skills By User using the
Skill Number field to create that relationship.

 

[Scott L. Heim [MSFT]]

Hi Adam,

Please accept my apologies but I still have a couple of questions regarding
the setup.

So the way I have the relationships now are as follows:

Category_Level --> Competency_Level (One to Many on CompetencyNumber
(Primary key) in Category_Level table to Competency_Numbers in
Competency_Level table)

Competency_Level --> Skills_By_Users (One to Many on Skill_Number (Primary
Key) in Competency_Level table to Skill_Numbers in Skills_By_Users table)

Is this correct? If so, how does the "Users_By_Info" table come into the
mix? Also, in regard to the 3 secondary data sources: where are those
fields coming from? Are they a combination of other tables?

I am sorry to keep coming back on this but the only way I can try to see
what you are seeing is to set this up properly.

Scott L. Heim
Microsoft Developer Support

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

 

[Adam Harding]

Scott

Users_by_Info links into Category_Level Via the Employment Number Key Field
on a 1-2-many link.

Other setup is completely correct.

The data source is three non-linked tables in one access dbase.

The first table "d:Category by job skills" has all the "categories" in.

The second table "d:Category-Sub by job skills" has all the "competencies"
matched with all the "categories" (ie a table with Systems:MSA in one row and
Qualifications:BA in the next where both "Systems" and "Qualifications" are
"categories" and "BA" and "MSA" are "Competencies").

The third and last data source is called "d:Category-Sub-Sub by job skills"
and has every "skill" listed next to its associate "competency" and
"Category" (ie one table with Systems:MSA:Authorisation on one row and the
next saying Qualifications:BA:2.1 where "2.1" and "Authorisation" are
skills,"MSA" and "BA" are competencies and "systems" and "qualifications" are
categories.)

I hope this makes sense it has sort of convoluted layout as i have cobbled
it together as i went along. Would i be better sourcing my data off the one
flat data structure "category-sub-sub for job skills" as it has ALL of the
info in. Or am i better leaving it as three tables. As you can see these do
not involve combinations of tables.

Scott don't worry about asking the questions I need the answer for delivery
this Tuesday.

ANY help received is greatefully received. As I am stumped on this one.

 

[Scott L. Heim [MSFT]]

Hi Adam,

OK - so is your InfoPath form "bound" to these 3 tables? In other words,
when you created the InfoPath solution did you choose "New from Data
Connection" and then add these 3 tables using the Wizard? Or as your
InfoPath solution created as a "New Blank Solution" and then you added
these 3 tables as secondary data connections?

If your InfoPath solution is indeed "bound" to these 3 tables did you then
add secondary data connections for each one again so you could use those
connections as the data source for your drop-down lists?

Lastly, you stated: "The first table d:Category by job skills" - where does
this table come from? In one of your original mails to me this table name
was not part of the design. Is this a different table or simply what you
named the "Category_Level" table when you used it as a data source?

Scott L. Heim
Microsoft Developer Support

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

 

[Scott L. Heim [MSFT]]

Hi Adam,

I did not get a post back from you yesterday so I was wondering if you seen
my last post:

Hi Adam,

OK - so is your InfoPath form "bound" to these 3 tables? In other words,
when you created the InfoPath solution did you choose "New from Data
Connection" and then add these 3 tables using the Wizard? Or as your
InfoPath solution created as a "New Blank Solution" and then you added
these 3 tables as secondary data connections?

If your InfoPath solution is indeed "bound" to these 3 tables did you then
add secondary data connections for each one again so you could use those
connections as the data source for your drop-down lists?

Lastly, you stated: "The first table d:Category by job skills" - where does
this table come from? In one of your original mails to me this table name
was not part of the design. Is this a different table or simply what you
named the "Category_Level" table when you used it as a data source?

Scott L. Heim
Microsoft Developer Support