Re: Issue with database size
- From: "Jeff Boyce" <nonsense@xxxxxxxxxxxx>
- Date: Mon, 29 Jan 2007 09:39:24 -0800
A couple alternatives ...
(First, I'm with Douglas, don't store image files in Access... but!)
The newest Access ('07) supposedly does a better job of handling image files
(i.e., less "bloat").
Or, if you can connect to a SQL-Server database, you could store the images
in SQL-Server. It will take a bit of coding to get them in and out... I've
used this approach for a "Contracts" database, to help reduce the need for
storing paper documents.
The alternative is to put the image files in a known location
(folder/directory/path), with a known naming convention, then store the
location/path/filename in your database.
Regards
Jeff Boyce
Microsoft Office/Access MVP
"pkost" <pkost@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:216D3ED7-2B39-4A8E-A221-D2EC33712420@xxxxxxxxxxxxxxxx
Hello all,
I'm interning on a database project that has become a lot more complicated
than planned. The goal is to store photos of the project I'm working for
and be able to use a form to call up all the photopoints over the past 4
years at the different locations. I'm having problems getting around
access's
2 gig limit. Which I thought I solved by creating lots of separate
databases
and linking them together but now I can't figure out how to write a query
in
which I don't pull in all the photos or is that even possible. Is there
anyway I can indirectly reference them and still get the pictures to show
up
in the forms? I'd appreciate any help. Thanks
.
- Prev by Date: Re: calculated field on a form
- Next by Date: Re: Using form calculations elsewere
- Previous by thread: Re: Issue with database size
- Next by thread: form print problem
- Index(es):
Relevant Pages
|
Loading
