linking forms

[Boodi]

Hi guys,

I really need ur help in this.

I have a form that its attributes are the primary keys of
other tables.
**Example: I have two tables the first one is
called "SYSTEM", the other one
called "DBMS". The relationship between them is many-to-
many, so I have to
have a bridge entity called "SYSTEM DBMS" containing the
primary keys of
both tables. The attributes below are the contents of
the "SYSTEM DBMS"
update form:

System code (a combo box that
displays the system code
from the system table or form [long integer])

DBMS Code (a combo box that
displays the DBMS code
from the DBMS table or form [long integer])

*** So the user need to know before he updates the data
access page (my
form), to know the system information before he starts
updating the records.
Also he needs to know what kind of DBMS the system is
working with, the
system can works on the same DBMS but Different versions.
My form just
displays the codes; I mean unmeaningfull codes just like
1 or 12.

*** What and how is the proper or the most convenient way
to help the user
other than adding a hyperlink to system update form and
DBMS form.

FYI, I am constructing my form by data access page not
form.


Thanx ...

 

[Tim Ferguson]

*** So the user need to know before he updates the data access page
(my form), to know the system information before he starts updating
the records. Also he needs to know what kind of DBMS the system is
working with, the system can works on the same DBMS but Different
versions. My form just displays the codes; I mean unmeaningfull codes
just like 1 or 12.

*** What and how is the proper or the most convenient way to help the
user other than adding a hyperlink to system update form and DBMS form

If you are really set on providing a separate form for this information,
then the simplest way is to provide a pair of listboxes. The first would
take its Rowsource from a query like this:

SELECT SystemID, OfficialName, Location
FROM Systems
ORDER BY OfficialName

If you like, you can of course hide the first column by setting the
columnwidth to "0;1.5in;1.5in". The second listbox would display the DBMS
information in a similar way. Navigating the table would be a bit odd, but
perhaps you've already sorted that out.

It's normal, though, to put this sort of stuff onto the Systems form or the
DMBS forms: use a subform and a query that contains the PK of the other
side and suitable user-readable information.

HTH


Tim F