MSAccess Cache - the best option?

[webbo]

Guys,

I'm currently in the design stages of a small application that will
gather information from external sources and cache the responses for
12 hours or so.

Obviously, the cache will need to be written to and queried - with
speed being the most important factor. I came to the conclusion that
a simple MS Access table could be used with a "cacheDate" field. The
problem with going down this route is that the user must have
Microsoft Data Access Components installed.

I have thought of other potential solutions; XML, INI etc. but all
fail on speed and query ability (it helps that SQL has built-in date
functions!).

I would like to ask everyone if they have ever had to cache "fetched"
data - and if so, how they went about storing it.

Cheers

James

[=?Utf-8?B?TWljaGVsIFBvc3NldGggW01DUF0=?=]

i would say loose Access and use sql server

yes the small footprint xcopy version ofcourse called sql compact
previously known as everywhere

http://www.microsoft.com/downloads/d...DisplayLang=en

"webbo" wrote:

Guys,

I'm currently in the design stages of a small application that will
gather information from external sources and cache the responses for
12 hours or so.

Obviously, the cache will need to be written to and queried - with
speed being the most important factor. I came to the conclusion that
a simple MS Access table could be used with a "cacheDate" field. The
problem with going down this route is that the user must have
Microsoft Data Access Components installed.

I have thought of other potential solutions; XML, INI etc. but all
fail on speed and query ability (it helps that SQL has built-in date
functions!).

I would like to ask everyone if they have ever had to cache "fetched"
data - and if so, how they went about storing it.

Cheers

James