Results 1 to 3 of 3
  1. #1
    2 Star Lounger
    Join Date
    Aug 2001
    Location
    Kent, England
    Posts
    108
    Thanks
    0
    Thanked 0 Times in 0 Posts

    General info for using Access (A2k)

    I currently use a product called Impromptu. This is essentially a report generator that I'm not a great fan of.

    I'm trying to wrate something in Access to handle some of the things that Impromptu just doesn't seem to be good at.

    I'm based in the UK and my core data resides on an SQL server in the States. The data on the server is updated once per week.

    My question is basically;

    What should I keep as an ODBC link & what should I Import?

    Is it purely based on the number of records in a table etc...

    The number of records in tables varies from about 20 to 150,000

    John

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: General info for using Access (A2k)

    To a large extent it depends on the speed of your link to SQL Server. If you have something that runs at LAN speed or thereabouts, I would start with everything using ODBC. (I presume when you said the server is updated once per week you meant the US based server, not a local UK server.)

    On the other hand, if you have a slower link, say 2048 or T1 or less, then you may want to import tables. If you have to pass lots of data to Access to generate the report, then the link will make things very sluggish. One thing you do want to avoid is doing queries that join a SQL/ODBC table with a local Access MDB table. Those are nearly always very slow. Hope this helps.
    Wendell

  3. #3
    Silver Lounger GARYPSWANSON's Avatar
    Join Date
    Aug 2001
    Location
    Frederick, Maryland, USA
    Posts
    1,788
    Thanks
    0
    Thanked 2 Times in 2 Posts

    Re: General info for using Access (A2k)

    I am surprised that you are not having luck using Impromptu. Are you using the product directly from Cognos, or from a third party provider?

    I have used Impromptu and Powerplay in the past and have never had a problem creating reports. Typically, when there was a problem, it was due to the personnel maintaining the data and not creating the correct groups of data or the user was not sure how to evaluate the data using the product.

    If impromptu is already working, wouldn't you just write a report to extract the data to import into Access as opposed to using ODBC Links. One option you might try if you are familiar with the background tables and data structures is to have the DBA copy the tables to a CD or send them to you in another manner.

    Good luck.
    Regards,

    Gary
    (It's been a while!)

Posting Permissions

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