StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In your comments to Haz and duffymo, you indicated your intention is to store "huge size images" in the database. That is not a best practice with MS Access. Due to the way images are stored, the db file size will increase by more than the size of the image files. Starting with Access 2007, there is an improved storage method which reduces that bloat, but it is still an issue. Furthermore this could be a deal-breaker, because the absolute hard-wired file size limit for an Access db file is 2 GB ... your database might not be able to accommodate enough huge images to meet your needs. </p> <p>I'm unclear about your concern over the need to install Access itself. With recent (since Win 2000) 32-bit Windows versions, the components required to use an Access db file are included as part of the operating system. If you're dealing with 64 bit Windows, you may need to get the <a href="http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23734" rel="nofollow">2007 Office System Driver: Data Connectivity Components</a></p> <p>Installing Access should only be required if your application uses Access for more than just data storage. An application which uses Access as the front-end client (with Access forms, reports, etc.) would require some form of Access to be installed, but it needn't be the full-blown version. You could design your application for the Access runtime version, which is free of cost starting with Access 2007:</p> <ol> <li><a href="http://www.microsoft.com/download/en/details.aspx?id=4438" rel="nofollow">Access 2007 Download: Access Runtime</a></li> <li><a href="http://www.microsoft.com/download/en/details.aspx?id=10910" rel="nofollow">Microsoft Access 2010 Runtime</a></li> </ol> <p>However, if you're using something else (e.g. Dot.Net) for your application front-end, you wouldn't need any form of Access installed.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload