Re: Two dbs using one linked table



"JohnB" <JohnB@xxxxxxxxxxxxxxx> wrote in
news:#$Vh6nccFHA.1044@xxxxxxxxxxxxxxxxxxxx:

> As I see it, I have two options. Either I could modify the existing db
> by adding new forms reports etc to make it dual purpose, or I could
> export the current db structure, minus data, to a new db and then
> modify the second db accordingly. The problem with this second option
> is there would then be data which is common to both dbs, held in just
> one table. A solution to this is to remove the common table from the
> second db and then set up a link to the original dbs table.

For me, this would be the clincher: if there is common data, then it's a
common database. It's not possible to enforce relational integrity across
two different mdb files, so you will in time find the MailingList users
happily deleting Customer records that still have outstanding Orders or
Invoices, etc.

Remember that there is no rule that you have to have only one front end.
It is very common to have different front end mdbs for the MailingList
people, the Finances, the Bookings and Management and so on, with
different sets of reports and forms in each.

> one? Each db would have a general database password but this may
> change at a later date to a more extensive type of security - any
> problems likely in that area?

File-level passwords are probably not even worth the mental effort it
takes to think of them in the first place. Either take the trouble to set
up full Access user-level security, or just educate your users. MDB
passwords are really a false safeguard.

Hope that helps


Tim F



.



Relevant Pages

  • Two dbs using one linked table
    ... Either I could modify the existing db by ... current db structure, minus data, to a new db and then modify the second db ... which is common to both dbs, ... original dbs table. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Copying a whole table
    ... To make the most of Access' capabilities, reconsider your data structure. ... This approach is very common ... ... consider the impact of simply adding a date/time field to your ... "links to reports" ...
    (microsoft.public.access.gettingstarted)
  • Re: Security advice needed!
    ... more common than you might imagine, though not nearly so common as it used ... Session variables are available only server-side, ... Are the passwords stored in the database in encrypted form or, ... Memory overhead could be a serious issue. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Yoko is an eyesore
    ... National Survey of Sexual attitudes & lifestyles') By K. Wellings et ... reports that 21.9% of British men are circumcised. ... I believe it is fair to say that it is common in the UK but obviously ...
    (rec.music.beatles)
  • Re: Yoko is an eyesore
    ... National Survey of Sexual attitudes & lifestyles') By K. Wellings et ... reports that 21.9% of British men are circumcised. ... Considerable variation was found between age and race, ... I believe it is fair to say that it is common in the UK but obviously ...
    (rec.music.beatles)