Results 1 to 7 of 7
  1. #1
    New Lounger
    Join Date
    Aug 2005
    Posts
    13
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Linking Front end to back end (Access 2002)

    Hi guys, i am writing a new system and would like to link front end to back end. The front end will be in crogram files and the back end will be in Cata.
    im going to have multiple backends in the data folder and have a seperate database with a table containing the paths to these datasets so that i can have a log in screen in the front end populated by this so that users can select which dataset they want to log into. does this sound a good idea or is there a better way of doing this?
    Also can anyone point me in the right direction code wise to do this, and the code for linking the tables to my front end.

    Gracias amigos

    Daryl <img src=/S/dizzy.gif border=0 alt=dizzy width=15 height=15>

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Linking Front end to back end (Access 2002)

    Do you have a specific reason for wanting to use multiple backends? Why not put all the tables in one backend?

  3. #3
    New Lounger
    Join Date
    Aug 2005
    Posts
    13
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Linking Front end to back end (Access 2002)

    it is because they are accounts and the data will be getting quite big so when they finish the financial year they want a new dataset

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Linking Front end to back end (Access 2002)

    Since you don't specify what "accounts" might be, it is hard to suggest alternatives, but separate back ends is a very bad one regardless. Just because they want to work with a new year's data doesn't mean they don't want to see a prior period for comparison purposes or a "last 12 months" history for a report. Users ask for what they want, but that should not determine how the data should be structured, since "they" usually know absolutely nothing about database design or the reasoning behind it. "Quite big" doesn't mean anything in particular and tends to depend on the perception of the person making the statement. I've seen it applied to 30Mb, which I consider a highly reasonable size, and to 100Mb, which is largish but not "quite big". At the 500Mb size, I start looking at alternatives.
    Charlotte

  5. #5
    New Lounger
    Join Date
    Aug 2005
    Posts
    13
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Linking Front end to back end (Access 2002)

    Basically it is a database for the Local Authority in a city to do project bugeting, a project lasts usually 3 - 4 years. they recieve 3 budgets, One amount for year one, another amount for years 2 and 3 together as a collective and a final one for year 4. It needs to be split into datasets for each of these groups as i have to report back on the speding or over spending variences as well as other bits. i need to be able to amalgamate everyones year 1 data into a single database so that it can be analysed by the dept director, as well as all the other data sets when the time comes. So i need to know how to link front to back. Also what would the best way be to merge 11 databases into one for data analysis? What is the maximum data size access can handle before it falls over?

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Linking Front end to back end (Access 2002)

    A single Access database can be up to 2 gigabytes in size. Since databases increase in size while you are working with them, it's wise to keep the compacted size well below that, say with a maximum of 500 MB to be on the safe side. You can store an awful lot of data in 500 MB, though.

    If you store all data in a single backend database, you can use queries to return data organized/split/combined in various ways for analysis and reporting. This is much easier than spreading the data over multiple backends and then combining them again.

    If the amount of data becomes much larger, it would be worth while switching to a server database system such as SQL Server. It can handle much larger databases and many more simultaneous users than Access. You could still use the Access frontend.

  7. #7
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Linking Front end to back end (Access 2002)

    A dataset is not the same thing as a database. Any number of datasets of various shapes and sizes can be created from a single combined database as Hans suggests in his reply. Your key question is
    <hr>Also what would the best way be to merge 11 databases into one for data analysis? <hr>
    and the answer is, to never separate the data in the first place. We can assist you in structuring the data if you provide more information about its shape and you will then be in a position to give your clients what they want without creating an impossible job for yourself.
    Charlotte

Posting Permissions

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