Welcome to SPN

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

Sign Up Now!

Access 2006; Is 2 Gig database limitation addressed ?

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

  1. mark mccurdy

    mark mccurdy
    Expand Collapse
    Guest

    Access 2003 and previous can't handle databases that reach 2 Gig in size.
    Only alternative that has worked is to break up tables and link various
    databases together. Sloppy. Issue still out there with Access 2006 ? Other
    options to address available ? Thanks.
     
  2. Loading...


  3. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    mark mccurdy wrote:
    > Access 2003 and previous can't handle databases that reach 2 Gig in
    > size. Only alternative that has worked is to break up tables and link
    > various databases together. Sloppy. Issue still out there with
    > Access 2006 ? Other options to address available ? Thanks.


    You sound like a candidate for an SQL server.

    --
    Joseph Meehan

    Dia duit
     
  4. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    mark mccurdy wrote:
    > Access 2003 and previous can't handle databases that reach 2 Gig in
    > size. Only alternative that has worked is to break up tables and link
    > various databases together. Sloppy. Issue still out there with
    > Access 2006 ? Other options to address available ? Thanks.


    Just to add to my prior message. I am assuming you have a properly
    normalized table design and have compacted the database, correct?

    --
    Joseph Meehan

    Dia duit
     
  5. mark mccurdy

    mark mccurdy
    Expand Collapse
    Guest

    Yes to both your questions. What you are telling me is at end of the day if
    my database is "flirting" with Access' 2 Gig limit that outside of what I
    have oulined that I am doign today, that going to SQL is my only option. I
    thought this was the case. Just wanted to confimr. thanks

    "Joseph Meehan" wrote:

    > mark mccurdy wrote:
    > > Access 2003 and previous can't handle databases that reach 2 Gig in
    > > size. Only alternative that has worked is to break up tables and link
    > > various databases together. Sloppy. Issue still out there with
    > > Access 2006 ? Other options to address available ? Thanks.

    >
    > Just to add to my prior message. I am assuming you have a properly
    > normalized table design and have compacted the database, correct?
    >
    > --
    > Joseph Meehan
    >
    > Dia duit
    >
    >
    >
     
  6. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    mark mccurdy wrote:
    > Yes to both your questions. What you are telling me is at end of the
    > day if my database is "flirting" with Access' 2 Gig limit that
    > outside of what I have oulined that I am doign today, that going to
    > SQL is my only option. I thought this was the case. Just wanted to
    > confimr. thanks


    Not exactly, I would tend to suggest that it is likely your best
    choice. :)


    >
    > "Joseph Meehan" wrote:
    >
    >> mark mccurdy wrote:
    >>> Access 2003 and previous can't handle databases that reach 2 Gig in
    >>> size. Only alternative that has worked is to break up tables and
    >>> link various databases together. Sloppy. Issue still out there with
    >>> Access 2006 ? Other options to address available ? Thanks.

    >>
    >> Just to add to my prior message. I am assuming you have a
    >> properly normalized table design and have compacted the database,
    >> correct?
    >>
    >> --
    >> Joseph Meehan
    >>
    >> Dia duit


    --
    Joseph Meehan

    Dia duit
     
  7. DBG

    DBG
    Expand Collapse
    Guest

    Mark-

    I just went through this recently, not because of a current database size
    problem but a future planning sort of deal.

    This quick discussion with Mary Chipman (MSFT) should provide some helpful
    direction and insights. I've essentially executed successfully what's
    described in the post below.

    http://www.microsoft.com/communitie...odbc&mid=cf37734c-23c8-4e7d-a801-3bd1b7351cda

    -David

    "mark mccurdy" wrote:

    > Yes to both your questions. What you are telling me is at end of the day if
    > my database is "flirting" with Access' 2 Gig limit that outside of what I
    > have oulined that I am doign today, that going to SQL is my only option. I
    > thought this was the case. Just wanted to confimr. thanks
    >
    > "Joseph Meehan" wrote:
    >
    > > mark mccurdy wrote:
    > > > Access 2003 and previous can't handle databases that reach 2 Gig in
    > > > size. Only alternative that has worked is to break up tables and link
    > > > various databases together. Sloppy. Issue still out there with
    > > > Access 2006 ? Other options to address available ? Thanks.

    > >
    > > Just to add to my prior message. I am assuming you have a properly
    > > normalized table design and have compacted the database, correct?
    > >
    > > --
    > > Joseph Meehan
    > >
    > > Dia duit
    > >
    > >
    > >
     

Share This Page