I've been battling with my grids again.

Here's a sample of my tables I'm working with:

SYSTEM.DBF (contains info on a specific piece of hardware, eg. mainframe, mini, server)
- hardwareid (unique i.d.)
- hardware info fields....

PERIPH.DBF (contains info on the peripherals attached to each "system")
- hardwareid (to relate each peripheral to a piece of hardware)
- peripheral type id (to relate to Allcodes.codeno to display "full name", i.e. 'Printer')
- vendor id (to relate to Allcodes.codeno to display "full name", i.e. 'Hewlett Packard')
- more peripheral info fields....

ALLCODES.DBF ("master" lookup data table for comboboxes etc.)
- codetype (type of 'code' such as peripheral, vendor, operating system to filter boxes)
- codeno (unique id)
- displayvalue ("full name" to be displayed on forms, i.e. "Hewlett Packard" or "DOS")

I've got multiple pages within my System form which lists data related to a "System". My form's data environment contains my SYSTEM.DBF, PERIPHERAL.DBF, SOFTWARE.DBF and ALLCODES.DBF tables. Each of the first 3 tables have several fields which need to look up display values from Allcodes.dbf for various comboboxes and grids throughout the pages. Allcodes.dbf contains all combobox display values for all my tables in my database as was suggested by the UT.

My question ... will I encounter any problems since I want multiple tables and fields to relate to my allmighty Allcodes.codeno field to pull up appropriate displayvalues in grids and comboboxes (some within the grids)?

What's the best way to establish these multiple relations... graphically in the DE or manually via code (and as always where do I put it?)?

As you can guess, I'm already encountering some problems and want to rule this option out.

MTIA!

Mandy