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  

Selective database splitting



 
 
Thread Tools Display Modes
  #1  
Old February 24th, 2010, 10:24 PM posted to microsoft.public.access.tablesdbdesign
DaveFrag
external usenet poster
 
Posts: 10
Default Selective database splitting

Is there a way to select the specific tables you want to split for sharing
across a network while other tables will remain local to each users system?
I specifically want to keep a version control table local to the system
rather than having it split with the other tables.
  #2  
Old February 24th, 2010, 11:30 PM posted to microsoft.public.access.tablesdbdesign
Dennis
external usenet poster
 
Posts: 1,222
Default Selective database splitting

Dave,

You can export individual tables from Tables windows. Right click on the
individual table and export it to the approrpriate backend.

The other option you have to to export everything and setup the links. Then
you can delete the local link to the approproate table and import just the
selected table(s) form the back end. I don't know how many tables you have
so I don't know which would be the fastest.

Good luck.

Dennis
  #3  
Old February 25th, 2010, 03:16 PM posted to microsoft.public.access.tablesdbdesign
DaveFrag
external usenet poster
 
Posts: 10
Default Selective database splitting

I appreciate your suggestion and did export the one table to my existing
back-end although how do I now link that table to the front-end so that it
knows that it's a linked table like the others?

"Dennis" wrote:

Dave,

You can export individual tables from Tables windows. Right click on the
individual table and export it to the approrpriate backend.

The other option you have to to export everything and setup the links. Then
you can delete the local link to the approproate table and import just the
selected table(s) form the back end. I don't know how many tables you have
so I don't know which would be the fastest.

Good luck.

Dennis

  #4  
Old February 25th, 2010, 09:27 PM posted to microsoft.public.access.tablesdbdesign
BruceM via AccessMonster.com
external usenet poster
 
Posts: 448
Default Selective database splitting

In Access 2003 (and 2000, I expect, and maybe earlier versions), Tools
Database Utilities Linked Table Manager. I think it will be clear enough
once you get there. For Access 2007, I'm afraid I do not know offhand.


DaveFrag wrote:
I appreciate your suggestion and did export the one table to my existing
back-end although how do I now link that table to the front-end so that it
knows that it's a linked table like the others?

Dave,

[quoted text clipped - 9 lines]

Dennis


--
Message posted via http://www.accessmonster.com

  #5  
Old February 28th, 2010, 07:18 AM posted to microsoft.public.access.tablesdbdesign
Armen Stein[_2_]
external usenet poster
 
Posts: 157
Default Selective database splitting

On Thu, 25 Feb 2010 20:27:34 GMT, "BruceM via AccessMonster.com"
u54429@uwe wrote:

In Access 2003 (and 2000, I expect, and maybe earlier versions), Tools
Database Utilities Linked Table Manager. I think it will be clear enough
once you get there. For Access 2007, I'm afraid I do not know offhand.


If you want a more automated approach to relinking tables, you're
welcome to use our free J Street Access Relinker on our J Street
Downloads page: http://ow.ly/M56Q. It's much nicer than Linked Table
Manager.

It handles multiple Access back-end databases, ignores ODBC linked
tables, and can automatically and silently relink to back-end
databases in the same folder as the application (handy for work
databases or single-user scenarios). There's a ReadMe table with
instructions.

It doesn't touch local tables, so you are free to use them for your
version control technique. We use local tables for things like that
too.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

 




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 12:15 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.