Results 1 to 10 of 10
  1. #1
    Join Date
    Jan 2008
    Posts
    4

    Red face Unanswered: Can Access accommodate 320,000 cells with data points?

    Can Access 2003 accommodate 320,000 cells with data points please?

    What does 320,000 cells with data points mean in terms of database rows please? Sorry if this sounds like a stupid question its just that I am more acquainted with using the term "rows" and not cells.

    Thank for your help in advance.

  2. #2
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Hi

    Welcome to the forum

    I think we will need more information - "320,000 cells with data points" has no meaning as far as relational databases are concerned. Are you converting a spreadsheet or sumfink?

  3. #3
    Join Date
    Jan 2008
    Posts
    4
    Thanks you for replying

    Apologies if the question seems vague, that was how the client posed the question to me i.e. "Can Access 2003 accommodate 320,000 cells with data points".

    I'm glad I'm not the only one stumped by the question, I will go back to them for more clarification.

  4. #4
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    I suspect they are used to working with spreadsheets and have got used to thinking about things in that way, using spreadsheet terminology.

  5. #5
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Table: MaybeOneAnswer
    ------------------------
    Field: Cell.
    Field: DataPoint.

    320,000 records.

    Yes, Access can support it.

    ? IF I understand the question!
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  6. #6
    Join Date
    Jan 2008
    Posts
    4

    Red face Can Access 2003 support 320,000 cells with datapoints

    Thanks you all and you were right they were using Excel speak.

    It's 320, 000 Excel cells (I'm told by the client that this equates to approx 4000 rows of data/80 tables)

    Now for the context of the original question - the client wants to deploy 320,000 Excel cells into Access locally for each user (200 users in total) so that they can generate analysis reports. Each user will work independently so therefore not networked. However they will be sending each other data on reports, data changes via email, in your opinion will this work?

    I have recommended that a relational database like SQL Server or Oracle may be more cost effective in the long term and it is a centralised system therefore no need to send emails to each other therefore reducing additional workload however Access is the strongly preferred choice for now.

    PS: Another question - Where can one find Access work estimators from please? I have given the client a rough estimate of 67 days for building the database including reports (I have included deployment to over 200 systems )

    (mods please let me know if its more appropriate to raise a new one)

  7. #7
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    If you are asking about how much to charge then we can't help. Supposedly the American government gets angry with us if we do. Try Googling perhaps. Or figure it out based on what you consider your time to be worth.

  8. #8
    Join Date
    Jan 2008
    Posts
    4
    No please perish the thought I'm not asking about how much to charge or how much my time is worth.

    I am creating a database project plan and I am trying to forecast how long it will take to complete the project I would appreciate any suggestions about tools that can be used to forecast how many hours or days a database project could take.

    PS: Please be aware that my query has nothing to do with how much to charge, I am aware of the rules of the group.

  9. #9
    Join Date
    Oct 2002
    Location
    Baghdad, Iraq
    Posts
    697
    Quote Originally Posted by olubunmi
    PS: Another question - Where can one find Access work estimators from please? I have given the client a rough estimate of 67 days for building the database including reports (I have included deployment to over 200 systems )

    (mods please let me know if its more appropriate to raise a new one)
    Well, you want to break it down into components, and then work out a kind of question / answer structure to it. E.g. what kind of schema does my data storage need? What kind of backup system will I need?

    Because once you've got an estimate of how many questions you've got to ask, all you have to do is figure out how long it takes a typical question to be answered on an discussion forum. A little math and, boom, you've got your answer.

    The best part is that all this is just more questions you can ask a discussion forum.

    I wonder why everyone doesn't work like this?

  10. #10
    Join Date
    Jun 2002
    Location
    Mpls/St.Paul area
    Posts
    303
    Estimations.

    Have the client help you create a software requirement specification.
    Identify the tables, the forms, and the reports.
    Determine the content of each of these objects.
    Carefully consider the additional time of deployment, feedback, documentation, corrections, network, security, backup plan, etc.

    When your analysis is solid, you all agree on what you want, you know what to do, you have considered your resources, you can estimate the time.

    Then double it.

    Yes, better to give a pessimistic time and meet it, the to be optomistic and explain several times to the client, why your are slipping.

Posting Permissions

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