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  

question about table placement in split database



 
 
Thread Tools Display Modes
  #1  
Old October 31st, 2008, 09:43 PM posted to microsoft.public.access.tablesdbdesign
dan dungan
external usenet poster
 
Posts: 67
Default question about table placement in split database

Hi,

I'm using Access 2000 on Windows 2000 professional to create a simple
reporting application. I split the database so I could put the mde
file on a couple users' computers.

Over the last year, I added more table to meet added requirements. But
I didn't add them to the _be file. Now I have some linked tables to
the _be file and some tables residing in the mdb file.

How might this impact the database function?

Thanks,

Dan
  #2  
Old October 31st, 2008, 10:54 PM posted to microsoft.public.access.tablesdbdesign
Daniel Pineault
external usenet poster
 
Posts: 658
Default question about table placement in split database

The basic idea of splitting the db into a front-end & back-end is to issue
each user with their own copy of the front-end. Amongst other things, this
means that when they open forms, report,... the code is run locally and
reduces network traffic and response time. With this in mind, in some cases
it can actually be preferable to add tables within the front-end to once
again speed up processes and reduce useless network traffic. These tables
however need to be static, meaning their content must not need to ever be
updated or the changes need not be distributed to other users.

A concrete example.
If I were to build a table for a list of cities my business works in, I
would never put it in the front-end, as over time I would need to add new
values for all of my staff to use.

If on the other hand I had a table containing a listing customer
'salutations' (ie:Mr, Mrs,...), I could place it in the front-end as this
table copuld easily be populated and would not need updates (unlikely at
least).

If implemented improperly, what could go wrong...
If you placed a table in the front-end that needs updating for all your
users, it will only update the local copy and as such will not be 'pushed' to
the other users. This can result in each user having their own set of
data...thus causing issues in the back-end (data not standardized...).

It is not a black or white question. It depends on your situation and needs.
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.



"dan dungan" wrote:

Hi,

I'm using Access 2000 on Windows 2000 professional to create a simple
reporting application. I split the database so I could put the mde
file on a couple users' computers.

Over the last year, I added more table to meet added requirements. But
I didn't add them to the _be file. Now I have some linked tables to
the _be file and some tables residing in the mdb file.

How might this impact the database function?

Thanks,

Dan

  #3  
Old November 3rd, 2008, 07:54 PM posted to microsoft.public.access.tablesdbdesign
dan dungan
external usenet poster
 
Posts: 67
Default question about table placement in split database

Thanks Daniel.

I'll consider what you've said.

Dan
 




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 05:50 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.