Database Size Limit

[John Taylor]

Tried to find any reference to this on the Microsoft help pages but can't
find any reference - maybe I'm just not smart enough to find it.

However; I have been working on a membership database where I "hold" a
photograph in a table. All is working as would expect so I won't bore you
with the details - it works almost identically to the Northwind sample
database "employee" table.

My problem that I get an error when I have about 30 photographs attached -
"database has exceeded size limits" or something like that. I know the
database is getting big (around 1G) and perhaps W2000 can't handle this size

Is there a limit to the size of an A2000 database? I'm running on W2000.

Thanks in advance for any information

John Taylor

[Allen Browne]

The theoretical limit is 2GB file size, but it's always a good idea to leave
yourself headroom.

In general, it's impractical to embed photos in an Access database like
that. Better to store the photos on the disk, and use a hyperlink field to
connect to them. You can load them into an Image control on a form as soon
as you visit the record, using code like this:
http://www.mvps.org/access/forms/frm0030.htm

If you really want to embed photos in your database, Access 2007 will do a
much better job of this:
a) It stores the photos compressed (which avoids much of the bloating
issue.)
b) The image control has a Control Source, so no code is needed to display
linked images.
c) You have the possibility of attaching multiple images to a record.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"John Taylor" <ja**@iinet.net .auwrote in message
news:45******** *************** @per-qv1-newsreader-01.iinet.net.au ...

Tried to find any reference to this on the Microsoft help pages but can't
find any reference - maybe I'm just not smart enough to find it.

However; I have been working on a membership database where I "hold" a
photograph in a table. All is working as would expect so I won't bore you
with the details - it works almost identically to the Northwind sample
database "employee" table.

My problem that I get an error when I have about 30 photographs
attached - "database has exceeded size limits" or something like that. I
know the database is getting big (around 1G) and perhaps W2000 can't
handle this size

Is there a limit to the size of an A2000 database? I'm running on W2000.

Thanks in advance for any information

John Taylor

[John Taylor]

Thanks Allen, usefull information as always.

A2007 is not an option for me at the moment so I'll have a look at the
coding you have pointed to me.

John Taylor


"Allen Browne" <Al*********@Se eSig.Invalidwro te in message
news:45******** *************** @per-qv1-newsreader-01.iinet.net.au ...

The theoretical limit is 2GB file size, but it's always a good idea to
leave yourself headroom.

In general, it's impractical to embed photos in an Access database like
that. Better to store the photos on the disk, and use a hyperlink field to
connect to them. You can load them into an Image control on a form as soon
as you visit the record, using code like this:
http://www.mvps.org/access/forms/frm0030.htm

If you really want to embed photos in your database, Access 2007 will do a
much better job of this:
a) It stores the photos compressed (which avoids much of the bloating
issue.)
b) The image control has a Control Source, so no code is needed to display
linked images.
c) You have the possibility of attaching multiple images to a record.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"John Taylor" <ja**@iinet.net .auwrote in message
news:45******** *************** @per-qv1-newsreader-01.iinet.net.au ...

>Tried to find any reference to this on the Microsoft help pages but can't
find any reference - maybe I'm just not smart enough to find it.

However; I have been working on a membership database where I "hold" a
photograph in a table. All is working as would expect so I won't bore you
with the details - it works almost identically to the Northwind sample
database "employee" table.

My problem that I get an error when I have about 30 photographs
attached - "database has exceeded size limits" or something like that. I
know the database is getting big (around 1G) and perhaps W2000 can't
handle this size

Is there a limit to the size of an A2000 database? I'm running on W2000.

Thanks in advance for any information

John Taylor

[Larry Linson]

"John Taylor" <ja**@iinet.net .auwrote

However; I have been working on a membership
database where I "hold" a photograph in a table. All
is working as would expect so I won't bore you
with the details - it works almost identically to the
Northwind sample database "employee" table.

My problem that I get an error when I have about
30 photographs attached - "database has exceeded
size limits" or something like that. I know the
database is getting big (around 1G) and perhaps
W2000 can't handle this size.

The sample imaging databases (applicable to Access 2003 and earlier
versions) at http://accdevel.tripod.com illustrate three approaches to
handling images in Access, and the download includes an article discussing
considerations in choosing an approach. Two of the approaches do not use OLE
Objects and, thus, avoid the database bloat, and some other problems,
associated with images in OLE Objects.

Not included in the sample is the option of using the "FollowHyperlin k" (for
which see Help) to display an image for which you have the
path-and-filename. Doing so will display using the image-handling software
that the user has registered for the image file type, but seems to have
fewer difficulties, all in all, than OLE Objects and Bound OLE Frame
Controls present.

If you are printing the images in reports, to avoid memory leakage, you
should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm.
PrintFailure.zi p is an Access97 MDB containing a report that fails during
the Access formatting process prior to being spooled to the Printer Driver.
This MDB also contains code showing how to convert the contents of the Image
control to a Bitmap file prior to printing. This helps alleviate the "Out of
Memory" error that can popup when printing image intensive reports.

Larry Linson
Microsoft Access MVP