one to one relationship

I need add a few fields in my table.
For some reson that I can not have all my users log off the systems.

I just wonder to create a one to one relationship table to add fields
and use same primary key and use join when I need the fields.

I just wonder are there any perfornance issue if I use one to one
relationship table instead of the fields are in the same tables.


Your help is great appreciated,

Well, vertical partitioning certainly can be useful when we have a wide
table and large amounts of rows (e.g. hundreds of thousands or
millions), but this is not something Jet really supports so the
potential gains are limited.

What you need to know is how and in what manners will you be querying.
If turns out that a large majority of your queries will span both
tables, then I'd say "forget it, keep it in a single table."

On the other hand, if your queries usually depend on knowing whether one
table has a certain record, then it may be worthwhile. But only if you
have several rows to justify the partitoning. Even a table with 50K rows
may not be enough for that justification.

Finally, it's almost always more work whether we do it with a wide table
or several one-one table... and is a sign of not optimally designed
tables. If you're not aware about normalization, I suggest you do go and
read up on it. Then that would render the whole question moot and leave
you with much simpler and managable solution.


inungh wrote:
I need add a few fields in my table.
For some reson that I can not have all my users log off the systems.

I just wonder to create a one to one relationship table to add fields
and use same primary key and use join when I need the fields.

I just wonder are there any perfornance issue if I use one to one
relationship table instead of the fields are in the same tables.


Your help is great appreciated,

Unless I am missing something:

I can't believe you can't have everyone off the "Production" database for 5
minutes to add a few fields.

That's what after 5:00 PM or weekends are for

"inungh" wrote:

I need add a few fields in my table.
For some reson that I can not have all my users log off the systems.

I just wonder to create a one to one relationship table to add fields
and use same primary key and use join when I need the fields.

I just wonder are there any perfornance issue if I use one to one
relationship table instead of the fields are in the same tables.


Your help is great appreciated,

Well, you could force your users out with something like my
"LogUsersOff.mdb" sample. You can find it he
http://www.rogersaccesslibrary.com/f...ts.asp?TID=328


--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"inungh" wrote in message
...
I need add a few fields in my table.
For some reson that I can not have all my users log off the systems.

I just wonder to create a one to one relationship table to add fields
and use same primary key and use join when I need the fields.

I just wonder are there any perfornance issue if I use one to one
relationship table instead of the fields are in the same tables.


Your help is great appreciated,

On Sep 24, 3:36*pm, "Roger Carlson"
wrote:
Well, you could force your users out with something like my
"LogUsersOff.mdb" sample. *You can find it hehttp://www.rogersaccesslibrary.com/f...ts.asp?TID=328

--
--Roger Carlson
* MS Access MVP
* Access Database Samples:www.rogersaccesslibrary.com
* Want answers to your Access questions in your Email?
* Free subscription:
*http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L

"inungh" wrote in message

...



I need add a few fields in my table.
For some reson that I can not have all my users log off the systems.

I just wonder to create a one to one relationship table to add fields
and use same primary key and use join when I need the fields.

I just wonder are there any perfornance issue if I use one to one
relationship table instead of the fields are in the same tables.

Your help is great appreciated,- Hide quoted text -

- Show quoted text -

Thanks all your help.
Finally, I have all my users off today and modified the tables.

About force users to log offapplications, users need activate the
application. If the computer is locked or user does not activate the
applications. will it work too?


Thanks again,