One backend or two?

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Jan
    #1

    One backend or two?

    I have a client that has two pretty distinct functions for which I'm
    developing databases. There are only a few staff in a small office. It
    looks like there are two tables that will be common to the two database
    systems, and the rest are completely different. It's clear to me that I
    want to develop two separate front-ends, one for each function. The
    only question is whether I should make two back-ends as well (with one
    having a link to the other for the two common tables), or use only one
    back-end, with both front-ends linked to it.

    I know it will work whichever way I do it, I'm only curious as to
    whether anyone has an opinion on which is the preferred approach.

    Thanks.

    Jan
    Tags: None
    • PC Datasheet
      #2
      Re: One backend or two?

      Jan,

      My recommendation is one BE. Just for the sake of simplicity.

      --
      PC Datasheet
      Your Resource For Help With Access, Excel And Word Applications
      resource@pcdata sheet.com
      https://www.pcdatasheet.com



      "Jan" <jan@stempelcon sulting.com> wrote in message
      news:115db7f6me 2hmdb@corp.supe rnews.com...[color=blue]
      > I have a client that has two pretty distinct functions for which I'm
      > developing databases. There are only a few staff in a small office. It
      > looks like there are two tables that will be common to the two database
      > systems, and the rest are completely different. It's clear to me that I
      > want to develop two separate front-ends, one for each function. The
      > only question is whether I should make two back-ends as well (with one
      > having a link to the other for the two common tables), or use only one
      > back-end, with both front-ends linked to it.
      >
      > I know it will work whichever way I do it, I'm only curious as to
      > whether anyone has an opinion on which is the preferred approach.
      >
      > Thanks.
      >
      > Jan[/color]


        Comment

        • MGFoster
          #3
          Re: One backend or two?

          -----BEGIN PGP SIGNED MESSAGE-----
          Hash: SHA1

          I'd use one back-end. That way you can set up referential integrity
          between the tables, which will ensure data integrity. With 2 back-ends
          you'd have a heterogeneous db, which cannot have referential integrity
          between tables.
          --
          MGFoster:::mgf0 0 <at> earthlink <decimal-point> net
          Oakland, CA (USA)

          -----BEGIN PGP SIGNATURE-----
          Version: PGP for Personal Privacy 5.0
          Charset: noconv

          iQA/AwUBQlbB54echKq OuFEgEQIqgQCfSk QTsmYvOo+8rqQP4 b8o2bKqKWwAoIul
          XQiZ35s0CG5WqUH UFOiPQgdq
          =+pLN
          -----END PGP SIGNATURE-----



          Jan wrote:[color=blue]
          > I have a client that has two pretty distinct functions for which I'm
          > developing databases. There are only a few staff in a small office. It
          > looks like there are two tables that will be common to the two database
          > systems, and the rest are completely different. It's clear to me that I
          > want to develop two separate front-ends, one for each function. The
          > only question is whether I should make two back-ends as well (with one
          > having a link to the other for the two common tables), or use only one
          > back-end, with both front-ends linked to it.
          >
          > I know it will work whichever way I do it, I'm only curious as to
          > whether anyone has an opinion on which is the preferred approach.[/color]

            Comment

            • dedejavu@hotmail.com
              #4
              Re: One backend or two?

              Save yourself a world of grief - use one BE.
              Save yourself another world of grief, use one front end and have the
              users choose the function they want.
              I do it with logins, the users can only see the forms they are allowed
              to.
              Developer Express has a free sidebar that really can help form
              management http://www.devexpress.com/Downloads/ActiveX/XSideBar/
              Good luck
              Pachydermitis

                Comment

                • paii, Ron
                  #5
                  Re: One backend or two?


                  <dedejavu@hotma il.com> wrote in message
                  news:1112984728 .608052.239870@ z14g2000cwz.goo glegroups.com.. .[color=blue]
                  > Save yourself a world of grief - use one BE.
                  > Save yourself another world of grief, use one front end and have the
                  > users choose the function they want.
                  > I do it with logins, the users can only see the forms they are allowed
                  > to.
                  > Developer Express has a free sidebar that really can help form
                  > management http://www.devexpress.com/Downloads/ActiveX/XSideBar/
                  > Good luck
                  > Pachydermitis
                  >[/color]

                  You don't even need a login, get the user name from the Windows login name

                  Environ$("UserN ame")



                    Comment

                    • dedejavu@hotmail.com
                      #6
                      Re: One backend or two?

                      true - unless more than one user uses that computer. e.g. receiving in
                      a warehouse.

                        Comment

                        Previous template Next
                        Working...