Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

BACKEND IN A PACKAGE

Discussion in 'Information Technology' started by Glint, Nov 1, 2005.

  1. Glint

    Glint
    Expand Collapse
    Guest

    Hi All,

    I developed a small program to keep the records of our small association. I
    split the database into a front and back-end before packaging it (because I
    cannot guarantee that all subsequent users will have Access). The idea is
    that when a current official leaves a post, he passes the back end
    (containing data) to the next official who can always get the front end to
    continue the job.

    After packaging however, I discovered that the back end was included in the
    package, thereby making the data in the package unretrievable for the next
    person. This was not my intention at all. All I want is for the front end to
    continue to write into a back end that can move from place to place,
    depending on whose turn it is to do the job.

    Can you suggest how I can achieve this?
    --
    Glint
     
  2. Loading...


  3. Arvin Meyer [MVP]

    Arvin Meyer [MVP]
    Expand Collapse
    Guest

    The installation files are merely text files and can be edited in notepad.
    Open the file, edit out the back-end references and delete the back-end mdb
    file.
    --
    Arvin Meyer, MCP, MVP
    Microsoft Access
    Free Access downloads
    http://www.datastrat.com
    http://www.mvps.org/access

    "Glint" <Glint@discussions.microsoft.com> wrote in message
    news:0843378D-0EFE-4428-8096-A0169C4524D6@microsoft.com...
    > Hi All,
    >
    > I developed a small program to keep the records of our small association.

    I
    > split the database into a front and back-end before packaging it (because

    I
    > cannot guarantee that all subsequent users will have Access). The idea is
    > that when a current official leaves a post, he passes the back end
    > (containing data) to the next official who can always get the front end to
    > continue the job.
    >
    > After packaging however, I discovered that the back end was included in

    the
    > package, thereby making the data in the package unretrievable for the next
    > person. This was not my intention at all. All I want is for the front end

    to
    > continue to write into a back end that can move from place to place,
    > depending on whose turn it is to do the job.
    >
    > Can you suggest how I can achieve this?
    > --
    > Glint
     
  4. Glint

    Glint
    Expand Collapse
    Guest

    Thanx Arvin,
    But I dont quite understand what you mean exactly. Which file do you want me
    to open for editing?
    --
    Glint


    "Arvin Meyer [MVP]" wrote:

    > The installation files are merely text files and can be edited in notepad.
    > Open the file, edit out the back-end references and delete the back-end mdb
    > file.
    > --
    > Arvin Meyer, MCP, MVP
    > Microsoft Access
    > Free Access downloads
    > http://www.datastrat.com
    > http://www.mvps.org/access
    >
    > "Glint" <Glint@discussions.microsoft.com> wrote in message
    > news:0843378D-0EFE-4428-8096-A0169C4524D6@microsoft.com...
    > > Hi All,
    > >
    > > I developed a small program to keep the records of our small association.

    > I
    > > split the database into a front and back-end before packaging it (because

    > I
    > > cannot guarantee that all subsequent users will have Access). The idea is
    > > that when a current official leaves a post, he passes the back end
    > > (containing data) to the next official who can always get the front end to
    > > continue the job.
    > >
    > > After packaging however, I discovered that the back end was included in

    > the
    > > package, thereby making the data in the package unretrievable for the next
    > > person. This was not my intention at all. All I want is for the front end

    > to
    > > continue to write into a back end that can move from place to place,
    > > depending on whose turn it is to do the job.
    > >
    > > Can you suggest how I can achieve this?
    > > --
    > > Glint

    >
    >
    >
     
  5. Glint

    Glint
    Expand Collapse
    Guest

    How do I connect the front end to the back end which I want to reside outside
    the package?
    --
    Glint


    "Arvin Meyer [MVP]" wrote:

    > The installation files are merely text files and can be edited in notepad.
    > Open the file, edit out the back-end references and delete the back-end mdb
    > file.
    > --
    > Arvin Meyer, MCP, MVP
    > Microsoft Access
    > Free Access downloads
    > http://www.datastrat.com
    > http://www.mvps.org/access
    >
    > "Glint" <Glint@discussions.microsoft.com> wrote in message
    > news:0843378D-0EFE-4428-8096-A0169C4524D6@microsoft.com...
    > > Hi All,
    > >
    > > I developed a small program to keep the records of our small association.

    > I
    > > split the database into a front and back-end before packaging it (because

    > I
    > > cannot guarantee that all subsequent users will have Access). The idea is
    > > that when a current official leaves a post, he passes the back end
    > > (containing data) to the next official who can always get the front end to
    > > continue the job.
    > >
    > > After packaging however, I discovered that the back end was included in

    > the
    > > package, thereby making the data in the package unretrievable for the next
    > > person. This was not my intention at all. All I want is for the front end

    > to
    > > continue to write into a back end that can move from place to place,
    > > depending on whose turn it is to do the job.
    > >
    > > Can you suggest how I can achieve this?
    > > --
    > > Glint

    >
    >
    >
     
  6. Albert D.Kallal

    Albert D.Kallal
    Expand Collapse
    Guest

    The simple solution is to NOT include the back end in the package.

    You then make a "separate" package for the back end. "data only" file.


    >All I want is for the front end to
    > continue to write into a back end that can move from place to place,
    > depending on whose turn it is to do the job.


    Either the users have to be taught to use the linke table manager if hte
    lcoation of hte ack end moves. And, if tnhey are using the runtime apckage,
    then you need to rool your own code that re-links the tables. The code that
    most of us use is here:

    http://www.mvps.org/access/tables/tbl0009.htm

    Often, the above is wrap-up in some nice routines that pops up the file
    dialog and allows the user to "browse" to the back end location...

    The code to popup the file dialog is here:

    http://www.mvps.org/access/api/api0001.htm

    There is additional goodies at that site. In a very short time, you can use
    the above code examples to "cobble" together you own nice re-linking
    routines...



    --
    Albert D. Kallal (Access MVP)
    Edmonton, Alberta Canada
    pleaseNOOSpamKallal@msn.com
    http://www.members.shaw.ca/AlbertKallal
     
  7. Glint

    Glint
    Expand Collapse
    Guest

    Oops!
    Looks like the back end in the package was a dummy afterall. On
    installation, the program did not find the back end in the expected path, and
    did not work. As soon as I put the back end in the original path intended for
    the program, the program worked fine. And so the active back end is not
    together with the front end in the package.
    I am sorry to have wasted your time. I was very apprehensive when I saw the
    back end in the package, and had assumed the front end would simply continue
    to link it right there.
    Thanx for your assistance.
    --
    Glint


    "Arvin Meyer [MVP]" wrote:

    > The installation files are merely text files and can be edited in notepad.
    > Open the file, edit out the back-end references and delete the back-end mdb
    > file.
    > --
    > Arvin Meyer, MCP, MVP
    > Microsoft Access
    > Free Access downloads
    > http://www.datastrat.com
    > http://www.mvps.org/access
    >
    > "Glint" <Glint@discussions.microsoft.com> wrote in message
    > news:0843378D-0EFE-4428-8096-A0169C4524D6@microsoft.com...
    > > Hi All,
    > >
    > > I developed a small program to keep the records of our small association.

    > I
    > > split the database into a front and back-end before packaging it (because

    > I
    > > cannot guarantee that all subsequent users will have Access). The idea is
    > > that when a current official leaves a post, he passes the back end
    > > (containing data) to the next official who can always get the front end to
    > > continue the job.
    > >
    > > After packaging however, I discovered that the back end was included in

    > the
    > > package, thereby making the data in the package unretrievable for the next
    > > person. This was not my intention at all. All I want is for the front end

    > to
    > > continue to write into a back end that can move from place to place,
    > > depending on whose turn it is to do the job.
    > >
    > > Can you suggest how I can achieve this?
    > > --
    > > Glint

    >
    >
    >
     

Share This Page