A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Design Question



 
 
Thread Tools Display Modes
  #1  
Old March 27th, 2008, 03:33 PM posted to microsoft.public.access.tablesdbdesign
jenniferspnc
external usenet poster
 
Posts: 65
Default Design Question

Sorry to post another question but I'm still thinking I've missed something,
only because I didn't realize the other piece of the puzzle.

I think seeing the "spreadsheet" of what exists today is handicapping my
design.

Please if somebody could help me understand. Right now, we have two
different offerings. Within each offering we have the same regions and
countries but the difference lies with the levels of support offered (4, one
no service, or null value). So I could have Offering 1...then shows
APAC....then showing the country Australia has 1st level of support. But on
the Offering 2 there is no service.

Again I have these tables,

Region_t
RegionID(PK), Region

Country_t
CountryID(PK), Country, RegionID(FK)

Support
SupportID(PK), Support Description, CountryID(FK), RegionID(FK) ---is this
right?

And how do I incorporate the 2 offerings? Does that start at top above
region? Do I include the offering as a FK in the Region table? Sorry I'm
lost and really trying to do things the right way. Since things are always
added on, I'm preparing for Languages spoken to be thrown my way, just wonder
if it would be easy to incorporate later on? Assuming it would be another
table, connected to region perhaps? I really appreciate everyone's help.



  #2  
Old March 27th, 2008, 04:06 PM posted to microsoft.public.access.tablesdbdesign
Evan Keel
external usenet poster
 
Posts: 46
Default Design Question

If you were to produce a report with columns Region, Country, Service, and
offering, what would it look like? Could you post this with sample data? I'm
having a hard time understanding your requirements. I'm sure the DB is quite
simple. And your table Support is wrong. If you know the Country, you know
the Region. I'm happy to help you, just help me understand your requiremts.
Again, a sample report with sample data would help.

Thanks,

Evan
"jenniferspnc" wrote in message
...
Sorry to post another question but I'm still thinking I've missed

something,
only because I didn't realize the other piece of the puzzle.

I think seeing the "spreadsheet" of what exists today is handicapping my
design.

Please if somebody could help me understand. Right now, we have two
different offerings. Within each offering we have the same regions and
countries but the difference lies with the levels of support offered (4,

one
no service, or null value). So I could have Offering 1...then shows
APAC....then showing the country Australia has 1st level of support. But

on
the Offering 2 there is no service.

Again I have these tables,

Region_t
RegionID(PK), Region

Country_t
CountryID(PK), Country, RegionID(FK)

Support
SupportID(PK), Support Description, CountryID(FK), RegionID(FK) ---is this
right?

And how do I incorporate the 2 offerings? Does that start at top above
region? Do I include the offering as a FK in the Region table? Sorry I'm
lost and really trying to do things the right way. Since things are

always
added on, I'm preparing for Languages spoken to be thrown my way, just

wonder
if it would be easy to incorporate later on? Assuming it would be another
table, connected to region perhaps? I really appreciate everyone's help.





  #3  
Old March 27th, 2008, 04:28 PM posted to microsoft.public.access.tablesdbdesign
jenniferspnc
external usenet poster
 
Posts: 65
Default Design Question

Sure, thanks for the help.

Here's a few lines from an Excel document of how it's displayed now.
Offering 1 Offering
2
(region) EMEA, APAC, America EMEA, APAC,
America
Australia Null, Level 1, Null Null,
Null, Null
Austria Level 2, Null, Null Level 1,
Null, Null

Not sure how the formatting appears in the message so I'll explain.
As you can see there is a level 1 support for Australia, in APAC, in the 1st
offering. There is no level of support currently entered for EMEA or America
(probably to be added at a future date, if at all).
At the same time Offering 2 has nothing for Australia in any of the Regions.

2nd example:
Looking at 1st offering. In Austria, region EMEA, there is Level 2 support
but nothing entered for APAC or America.
On second offering, in Austria, Region EMEA, Level 1 Support is offered but
nothing for APAC or America..

Hope this helps clarify what I'm looking to achieve. Thank you!

"Evan Keel" wrote:

If you were to produce a report with columns Region, Country, Service, and
offering, what would it look like? Could you post this with sample data? I'm
having a hard time understanding your requirements. I'm sure the DB is quite
simple. And your table Support is wrong. If you know the Country, you know
the Region. I'm happy to help you, just help me understand your requiremts.
Again, a sample report with sample data would help.

Thanks,

Evan
"jenniferspnc" wrote in message
...
Sorry to post another question but I'm still thinking I've missed

something,
only because I didn't realize the other piece of the puzzle.

I think seeing the "spreadsheet" of what exists today is handicapping my
design.

Please if somebody could help me understand. Right now, we have two
different offerings. Within each offering we have the same regions and
countries but the difference lies with the levels of support offered (4,

one
no service, or null value). So I could have Offering 1...then shows
APAC....then showing the country Australia has 1st level of support. But

on
the Offering 2 there is no service.

Again I have these tables,

Region_t
RegionID(PK), Region

Country_t
CountryID(PK), Country, RegionID(FK)

Support
SupportID(PK), Support Description, CountryID(FK), RegionID(FK) ---is this
right?

And how do I incorporate the 2 offerings? Does that start at top above
region? Do I include the offering as a FK in the Region table? Sorry I'm
lost and really trying to do things the right way. Since things are

always
added on, I'm preparing for Languages spoken to be thrown my way, just

wonder
if it would be easy to incorporate later on? Assuming it would be another
table, connected to region perhaps? I really appreciate everyone's help.






  #4  
Old March 27th, 2008, 05:34 PM posted to microsoft.public.access.tablesdbdesign
Evan Keel
external usenet poster
 
Posts: 46
Default Design Question


"jenniferspnc" wrote in message
...
Sure, thanks for the help.

Here's a few lines from an Excel document of how it's displayed now.
Offering 1

Offering
2
(region) EMEA, APAC, America EMEA, APAC,
America
Australia Null, Level 1, Null Null,
Null, Null
Austria Level 2, Null, Null Level 1,
Null, Null

Not sure how the formatting appears in the message so I'll explain.
As you can see there is a level 1 support for Australia, in APAC, in the

1st
offering. There is no level of support currently entered for EMEA or

America
(probably to be added at a future date, if at all).
At the same time Offering 2 has nothing for Australia in any of the

Regions.

I thought the relationship between Region and Country was 1 to Many. One
Region contains many Countrys. A Country belongs to one Region. How can
Austrailia have a support level for Regions EMEA and America if it belongs
to Region APAC?

Evan


  #5  
Old March 27th, 2008, 06:28 PM posted to microsoft.public.access.tablesdbdesign
jenniferspnc
external usenet poster
 
Posts: 65
Default Design Question

Yes, sorry that's right, I was looking at another tab that had actual support
locations in one area supporting multiple countries and getting it all
confused....but that is a separate table that i'm using just to print office
locations, I won't be tying that in (there's so much information in this one
excel document)....

So for this specific one, country is associated with only one region and can
have varying level of support based on which offering it appears under..that
should make it work. As you stated, yes, one region can have many locations
but a location can only be associated with one region.

"Evan Keel" wrote:


"jenniferspnc" wrote in message
...
Sure, thanks for the help.

Here's a few lines from an Excel document of how it's displayed now.
Offering 1

Offering
2
(region) EMEA, APAC, America EMEA, APAC,
America
Australia Null, Level 1, Null Null,
Null, Null
Austria Level 2, Null, Null Level 1,
Null, Null

Not sure how the formatting appears in the message so I'll explain.
As you can see there is a level 1 support for Australia, in APAC, in the

1st
offering. There is no level of support currently entered for EMEA or

America
(probably to be added at a future date, if at all).
At the same time Offering 2 has nothing for Australia in any of the

Regions.

I thought the relationship between Region and Country was 1 to Many. One
Region contains many Countrys. A Country belongs to one Region. How can
Austrailia have a support level for Regions EMEA and America if it belongs
to Region APAC?

Evan



  #6  
Old March 27th, 2008, 06:52 PM posted to microsoft.public.access.tablesdbdesign
Evan Keel
external usenet poster
 
Posts: 46
Default Design Question

Ok, I think I understand. Your tables would look like this:

Region_t
RegiondID (PK)

Country_t
CountryID (PK)
Country
RegionID (FK)

Support_t
SupportID (PK)
SupportDescription

CountryOfferings_t
CountryID (PK)
OfferNumber(PK) (Sequential number)
SupportID (FK)

This allows for any number of offers and only one Support type per offer.

It can be too easy to think in terms of a spreadsheet. As you know, to get
the spreadsheet look you would need use a cross-tab query.

Do you really need to append "-t" to table names?

Hope this helped.

Evan
"jenniferspnc" wrote in message
news
Yes, sorry that's right, I was looking at another tab that had actual

support
locations in one area supporting multiple countries and getting it all
confused....but that is a separate table that i'm using just to print

office
locations, I won't be tying that in (there's so much information in this

one
excel document)....

So for this specific one, country is associated with only one region and

can
have varying level of support based on which offering it appears

under..that
should make it work. As you stated, yes, one region can have many

locations
but a location can only be associated with one region.

"Evan Keel" wrote:


"jenniferspnc" wrote in message
...
Sure, thanks for the help.

Here's a few lines from an Excel document of how it's displayed now.
Offering 1

Offering
2
(region) EMEA, APAC, America EMEA,

APAC,
America
Australia Null, Level 1, Null Null,
Null, Null
Austria Level 2, Null, Null Level

1,
Null, Null

Not sure how the formatting appears in the message so I'll explain.
As you can see there is a level 1 support for Australia, in APAC, in

the
1st
offering. There is no level of support currently entered for EMEA or

America
(probably to be added at a future date, if at all).
At the same time Offering 2 has nothing for Australia in any of the

Regions.

I thought the relationship between Region and Country was 1 to Many. One
Region contains many Countrys. A Country belongs to one Region. How can
Austrailia have a support level for Regions EMEA and America if it

belongs
to Region APAC?

Evan





 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 03:40 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.