Need some advise

[Johnny]

Hello everybody,

I have a DB where I'm trying to manage information flow:

This is the scenario:

When some information is registered, the person who register need to
store on the table the user to whom the info. concerns.
I've created a field on InfoTbl to store UserID, and here arises the
problem.
If the info is to be sent to just one user everything works well, but
if the info. must be sent to more than one user I can´t have have
ideas how to store on the table.
I guess that wouldn't be good practice to have in the table
UserID1,UserID2,UserID3.....

So, I request your help in two subjects:
1. How should the person who registers info select user to inform.
2. How to store the info for more than one user and where!

Thanks in advance
Johnny

 

[Arvin Meyer MVP]

It looks like you have a many-to-many relationship. In Access that is easily
handled with a junction table which uses a compound primary key consisting
of the primary key from each of the 2 other tables. An example of junction
tables is in the Northwind sample database that comes with Access. Look at
the relationship window for the OrderDetails table to see how the
connections are made.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


Hello everybody,

I have a DB where I'm trying to manage information flow:

This is the scenario:

When some information is registered, the person who register need to
store on the table the user to whom the info. concerns.
I've created a field on InfoTbl to store UserID, and here arises the
problem.
If the info is to be sent to just one user everything works well, but
if the info. must be sent to more than one user I can´t have have
ideas how to store on the table.
I guess that wouldn't be good practice to have in the table
UserID1,UserID2,UserID3.....

So, I request your help in two subjects:
1. How should the person who registers info select user to inform.
2. How to store the info for more than one user and where!

Thanks in advance
Johnny

 

[Johnny]

It looks like you have a many-to-many relationship. In Access that is easily
handled with a junction table which uses a compound primary key consisting
of the primary key from each of the 2 other tables. An example of junction
tables is in the Northwind sample database that comes with Access. Look at
the relationship window for the OrderDetails table to see how the
connections are made.
--
Arvin Meyer, MCP, MVPhttp://www.datastrat.comhttp://www.mvps.org/accesshttp://www.accessmvp.com


Hello everybody,

I have a DB where I'm trying to manage information flow:

This is the scenario:

When some information is registered, the person who register need to
store on the table the user to whom the info. concerns.
I've created a field on InfoTbl to store UserID, and here arises the
problem.
If the info is to be sent to just one user everything works well, but
if the info. must be sent to more than one user I can´t have have
ideas how to store on the table.
I guess that wouldn't be good practice to have in the table
UserID1,UserID2,UserID3.....

So, I request your help in two subjects:
1. How should the person who registers info select user to inform.
2. How to store the info for more than one user and where!

Thanks in advance
Johnny

Hello Arvin,

Thank you for replay, I will try you sugestion, but first place I have
som difficulty setting up the bullet 1. on my first post.
I have a users table, and I want tu use this table to pick up the
users to whom the info is to be sent.
I have other table (InfoTbl) where I store the info.
As I said, I need to advise users that some new info is available, not
all users, some times just one user other times 2 or 3 users, and here
is my problem. If the info concerns only for one user the solution was
simple, I would store the UserID, on the InfoTbl, on the record
related with that specific info. But sometimes info concerns to 2 or
more users, and I don't know how to store in this case. Probably I
need to create another table (InfoToUsersTbl) that will relate
UsersTbl and InfoTbl as you sugest. But how should I fill up the
InfoToUsersTbl. I remember that I must pick the users in the moment
I'm registring the information.

Appreciate you help
Thank you
Johnny

 

[Arvin Meyer MVP]

Thank you for replay, I will try you sugestion, but first place I have
som difficulty setting up the bullet 1. on my first post.
I have a users table, and I want tu use this table to pick up the
users to whom the info is to be sent.
I have other table (InfoTbl) where I store the info.
As I said, I need to advise users that some new info is available, not
all users, some times just one user other times 2 or 3 users, and here
is my problem. If the info concerns only for one user the solution was
simple, I would store the UserID, on the InfoTbl, on the record
related with that specific info. But sometimes info concerns to 2 or
more users, and I don't know how to store in this case. Probably I
need to create another table (InfoToUsersTbl) that will relate
UsersTbl and InfoTbl as you sugest. But how should I fill up the
InfoToUsersTbl. I remember that I must pick the users in the moment
I'm registring the information.

The best way to enter the information is using a form to enter InfoTbl with
a subform, containing a combo box to enter the users (with the link field
from InfoTbl) into the InfoUsers.