Sharing Tables.

[Tim]

Hi

I'm wondering what is the best way to do the following.

I have 2 tables, InternalOrders & ExternalOrders one of
the fields is the same in both tables. "Status"

So the following:

Table 1:
InternalOrders
iStatus

Table 2:
ExternalOrders
eStatus

I want to use the same status messages for each to keep
consistnacy.. so I made a 3rd table called sStatus (the
little s signifies Shared for me purpose)

So the Following:

Table 3:
sStatus
sStatus


So I want eStatus and iStatus to get there information from
sStatus Table.. I know I can set eStatus and iStatus to
be Data Type lookup, but I've read that this is not a good
idea.

Can I set iStatus and eStatus to Data Type Text and then
set the lookup to be combo.. Or is this the same as just
setting the Data Type to Lookup??

What would be the correct way to do this.

Thanks in advance

 

[Eric Butts [MSFT]]

Hi Tim,

I see no problem in making it a lookup value pulling from that table. Is
there something you've read/heard otherwise?

Regards,

Eric Butts
Microsoft Access Support
(e-mail address removed)
"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
<http://www.microsoft.com/security/security_bulletins/ms03-026.asp> and/or
to visit Windows Update at <http://windowsupdate.microsoft.com/> to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."

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

--------------------
| Content-Class: urn:content-classes:message
| From: "Tim" <[email protected]>
| Sender: "Tim" <[email protected]>
| Subject: Sharing Tables.
| Date: Tue, 13 Jul 2004 12:02:08 -0700
| Lines: 41
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcRpC+VyC4pQuYYNRo+oti+rnBukAQ==
| Newsgroups: microsoft.public.access.tablesdbdesign
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.access.tablesdbdesign:81758
| NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
| X-Tomcat-NG: microsoft.public.access.tablesdbdesign
|
| Hi
|
| I'm wondering what is the best way to do the following.
|
| I have 2 tables, InternalOrders & ExternalOrders one of
| the fields is the same in both tables. "Status"
|
| So the following:
|
| Table 1:
| InternalOrders
| iStatus
|
| Table 2:
| ExternalOrders
| eStatus
|
| I want to use the same status messages for each to keep
| consistnacy.. so I made a 3rd table called sStatus (the
| little s signifies Shared for me purpose)
|
| So the Following:
|
| Table 3:
| sStatus
| sStatus
|
|
| So I want eStatus and iStatus to get there information from
| sStatus Table.. I know I can set eStatus and iStatus to
| be Data Type lookup, but I've read that this is not a good
| idea.
|
| Can I set iStatus and eStatus to Data Type Text and then
| set the lookup to be combo.. Or is this the same as just
| setting the Data Type to Lookup??
|
| What would be the correct way to do this.
|
| Thanks in advance
|
|

 

[John Vinson]

So I want eStatus and iStatus to get there information from
sStatus Table.. I know I can set eStatus and iStatus to
be Data Type lookup, but I've read that this is not a good
idea.

Can I set iStatus and eStatus to Data Type Text and then
set the lookup to be combo.. Or is this the same as just
setting the Data Type to Lookup??

Yes, it is. See http://www.mvps.org/access/lookupfields.htm for a
critique of the lookup datatype.

The biggest disadvantage of lookups, IMHO, is that they encourage the
use of table datasheets for data viewing and editing - an
inappropriate thing to do! Use Forms (with combo boxes of course)
instead; leave the datasheets showing the actual content of the table
instead of concealing that content behind a lookup.