Results 1 to 2 of 2
  1. #1
    2 Star Lounger
    Join Date
    Feb 2003
    Posts
    120
    Thanks
    3
    Thanked 2 Times in 2 Posts
    Is there some clever migration path when one hits the 2GB size limit on Access 2007? The large size is caused by photos. I'd prefer not to split the database into 2 or 3 pieces, but I can if that's the "normal" way of handling this situation.
    Thanks
    Bob Chapman

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts
    As you suggest, one way is to split the database into two or three (or more) backends, and then use a Union query in the front-end to view the complete set of records. Another option is to store a path to the actual graphics file in the table, rather than using OLE fields. The third options is to use the .ACCDB format and use Attachment as the datatype - the bloat is significantly reduced. Finally you might consider using SQL Server 2008 Express as it works a bit nicer with BLOB data types, and has larger storage limits (10 GB for R2).
    Wendell

Posting Permissions

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