Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2003
    Posts
    13

    Unanswered: Data succession-passing db tables to new operators

    I am preparing a database application that will be used by one person in an organization. Frequently , (every year or two) the program will be given to another (usually a laptop) user in the organization as that person assumes the task of the program’s operation and responsibilities.

    I would like the user to load the program from the installation CD (made with Wise Installation System and SageKey softwares) on each computer each time there is a brand new user and each time a subsequent user takes over. However, each successive user needs to have the data files passed from the last user.

    At face value it seems that having a front end/back end arrangement might be the most desirable. Can anyone jump start me on the best way to accomplish this process to EZ data transfer?

    Thanks in advance to all,

    JQ

  2. #2
    Join Date
    Mar 2003
    Location
    The Bottom of The Barrel
    Posts
    6,102
    Provided Answers: 1
    Could you go into a bit more (read: SOME) detail about how your "database application" is structured? It could be as simple as copying a file from one place to another, it could be as complex as establishing a connection to a remote server, who knows...
    oh yeah... documentation... I have heard of that.

    *** What Do You Want In The MS Access Forum? ***

  3. #3
    Join Date
    Sep 2003
    Posts
    13

    Data succession; transfer data

    Quote Originally Posted by Teddy
    Could you go into a bit more (read: SOME) detail about how your "database application" is structured? It could be as simple as copying a file from one place to another, it could be as complex as establishing a connection to a remote server, who knows...
    Desktop application, not for a network. 1 license for an organization, only 1 user per license. Used by small organizations, little tech savvy. No networks present generally.

    The application is modified slightly with each license as I embed company logos, photos, and text that cannot be changed. This takes care of a few of security issues -- all reports, screens show CompanyA's headers. However, I suppose I could place some, if not all, of these in a GlobalCode module.

    For passing along data, my preference is for recording to CD and passing it along, but could also be done email attachment, or some type of network transfer.

    I have not used ADO, but have used DAO throughout.

    I have some tables that are sensitive to the customer and the licensing, which made for a hesitancy to split off all of the tables.

    Great need for simplicity in data succession transfer. Three rules for my audience: 1. keep it simple, 2. keep it simple, and 3. keep it simpler.

    What other structure can I tell you? Thanks for the interest.

    --JQ

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •