Xml Vs Access

[virtuapete]

I have a database of roughly 5000 company records. related to each of
those records are multiple-per-company records of products. for both
the products and the companies i would like to store reviews and
descriptions. there would be one description per company and product
but multiple reviews of both. I have the records all stored in Access
at the moment, but i am hesitant to store the descriptions/reviews in
the same database because of speed and file size. Would i be better
off storing all the descriptions/reviews in XML and just call them when
the particular record is retrieved? or would it be fine to just store
all those in a separate database? maybe just another table will do?
what is the best way to structure this?
--
virtuapetePosted from http://www.pcreview.co.uk/ newsgroup access

[Cor Ligthert]

Pete,

Absolute not, in XML you can only do changes by renewing the complete file.

You can think about MSDE as a substitute (although that has a size limit
from what I am not sure anymore 2 or 4GB).

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

[Tobin Harris]

I'd be tempted to carry on in Access, making sure you're data structure is
somewhat normalised. As a guess, this would probably mean creating tables
called CompanyReviews and ProductReviews. If your file sizes actually become
painful, or Access becomes too slow, it's fairly easy to migrate to another
database such as MSDE.

Tobes


"virtuapete" <virtuapete.1qty1y@> wrote in message
news:h-********************@giganews.com...

I have a database of roughly 5000 company records. related to each of
those records are multiple-per-company records of products. for both
the products and the companies i would like to store reviews and
descriptions. there would be one description per company and product
but multiple reviews of both. I have the records all stored in Access
at the moment, but i am hesitant to store the descriptions/reviews in
the same database because of speed and file size. Would i be better
off storing all the descriptions/reviews in XML and just call them when
the particular record is retrieved? or would it be fine to just store
all those in a separate database? maybe just another table will do?
what is the best way to structure this?
--
virtuapetePosted from http://www.pcreview.co.uk/ newsgroup access

[aatcbbtccctc]

Access (by which you probably mean Jet, the default underlying database
engine for Access) will readily handle orders of magnitude more than
the # of records you talk of.

Just make sure the db schema is properly designed (ie. normalized) &
that each table has a defined primary key (which will cause it to be
indexed).

HTH,
TC