Welcome to SPN

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

Sign Up Now!

please help!

Discussion in 'Information Technology' started by aheath15, Jul 28, 2006.

Tags:
  1. aheath15

    aheath15
    Expand Collapse
    Guest

    I'm not sure if this is possible but if anyone has any ideas that could even
    slightly apply, I would highly appreciate them....

    My database allows a user to create an order by selecting various products
    from a form. These selections go through a series of queries to 'fool proof'
    the order and then are fed into a report.

    After the report is finished, I need to make sure it is not altered when
    creating a new order, and to do this I am thinking I should export it to
    another file so it is not inadvertenly changed. HOWEVER---this is my
    problem-----orders rarely stay the same from order date to ship date, so this
    report will likely be changed a number of times. THUS, it needs to be in a
    file that will retain the relationships with the 'master' database. How can
    I do this? I know I can link databases, but I do not want the report to be
    changed when creating another order. (I.E. can I turn relationships on and
    off when necessary?? ...ON when I want to update orders, and OFF when I want
    to create entirely new ones)

    I know this can be accomplished by copying the entire database into a new
    file, however this will take up too much space, considering the amount of
    orders that will be dealt with. Any ideas??

    Thanks!
     
  2. Loading...

    Similar Threads Forum Date
    General Help! Looking for a good clairvoyant/card reader......any suggestions? Please Blogs Jan 25, 2016
    Please help Questions and Answers Nov 1, 2013
    Please Help! What is the Name of the Narrator/Raagi? Gurbani Download Oct 16, 2012
    Muslim Girl-Sikh Boy Marriage Problems- Please Help! Love & Marriage Oct 12, 2012
    Help Please :/ Relationships Apr 19, 2011

  3. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Mon, 22 May 2006 08:48:01 -0700, aheath15
    <aheath15@discussions.microsoft.com> wrote:

    >After the report is finished, I need to make sure it is not altered when
    >creating a new order, and to do this I am thinking I should export it to
    >another file so it is not inadvertenly changed. HOWEVER---this is my
    >problem-----orders rarely stay the same from order date to ship date, so this
    >report will likely be changed a number of times.


    Now I'm confused.

    You say you want to "make suer it is not altered" and then say "likely
    to be changed a number of times".

    Which do you want??? To protect the data in the table from change, or
    to allow changes?

    John W. Vinson[MVP]
     
  4. aheath15

    aheath15
    Expand Collapse
    Guest

    I understand your confusion, but I actually want it to do both.

    We need to have all previous order reports on file reference, thus we need
    it saved somewhere where it cannot be altered, or at least stored in a
    separate file that takes up minimal hard drive space.

    At the same time, the relations must be able to exist in case the order
    needs to be changed.

    I have been messing around with saving the report in various places.
    Ideally, I would like to be able to save JUST the report in a file. If it
    needs to be updated, I would like to just import that report back into the
    main database for updating. Once updated, I would like to export it back to
    its 'holding' place.

    I'm not sure if this is making any better sense. Whenever I try to export
    just the report, I cannot open it in another file unless I take all the
    tables/etc- with it, which makes the file too big.

    Please let me know if you have any suggestions, I really appreciate your help!

    "John Vinson" wrote:

    > On Mon, 22 May 2006 08:48:01 -0700, aheath15
    > <aheath15@discussions.microsoft.com> wrote:
    >
    > >After the report is finished, I need to make sure it is not altered when
    > >creating a new order, and to do this I am thinking I should export it to
    > >another file so it is not inadvertenly changed. HOWEVER---this is my
    > >problem-----orders rarely stay the same from order date to ship date, so this
    > >report will likely be changed a number of times.

    >
    > Now I'm confused.
    >
    > You say you want to "make suer it is not altered" and then say "likely
    > to be changed a number of times".
    >
    > Which do you want??? To protect the data in the table from change, or
    > to allow changes?
    >
    > John W. Vinson[MVP]
    >
     
  5. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Mon, 22 May 2006 12:15:01 -0700, aheath15
    <aheath15@discussions.microsoft.com> wrote:

    >I understand your confusion, but I actually want it to do both.
    >
    >We need to have all previous order reports on file reference, thus we need
    >it saved somewhere where it cannot be altered, or at least stored in a
    >separate file that takes up minimal hard drive space.
    >
    >At the same time, the relations must be able to exist in case the order
    >needs to be changed.
    >
    >I have been messing around with saving the report in various places.
    >Ideally, I would like to be able to save JUST the report in a file. If it
    >needs to be updated, I would like to just import that report back into the
    >main database for updating. Once updated, I would like to export it back to
    >its 'holding' place.
    >
    >I'm not sure if this is making any better sense. Whenever I try to export
    >just the report, I cannot open it in another file unless I take all the
    >tables/etc- with it, which makes the file too big.
    >
    >Please let me know if you have any suggestions, I really appreciate your help!


    Well, let's get clear what it is that you want to preserve.

    An Access Report is not "stored data". It's a way to pull information
    together for presentation on paper.

    What you need to store is nto "the report" - but the data which is
    displayed on the report. If you have that stored, you can regenerate
    the report at any time!

    Without knowing about these updates, all I can suggest is that you
    need to design your table structures so that you can keep (long term)
    the data which went into the report; and then - in a separate table,
    or separate records in the same table with a datestamp indicating when
    they changed - the modified data.

    This may be a bit tricky to set up, perhaps more so than is
    appropriate for this venue, but that's the route I'd take: concentrate
    on storing *the data*, not "the report".

    John W. Vinson[MVP]
     

Share This Page