Now we agree again (completely)
Cor
Disagreed Tom,
I once started with Net like Ed and that was with using an XML file to do
things (which became very quick a dataset).
Horrible to get that well because that you have to check that it is always
completely right rewritten.
I guess I should say, that I would actually use a database solution
for this as well. I was only commenting on Scott's comments on file
locking.
I checked this thread because I have given Ed a solution how to use a CSV
file. But that has the same problems as an XML file or any serial file.
I mentioned the office xml, because I think for simple readonly data
as he's talking about is a much simpler solution. Especially when
using LINQ to XML. I would post code, but all of my stuff is in C#.
I have code to generate xml spreadsheets as well as read them. I also
have some code I've been working on to convert Microsoft Word XML
documents to WPF FlowDocuments.
Of course, xml has the same problems if you are having to lock the
file - what I was pointing out is that the OP is using the data in a
read only fashion. But, using the OLEDB reader could introduce
problems IF it performs file locking. Simply having two vistors hit
the site at the sametime can cause issues in that case. Using simple
file io, you can control that by opening the file in shared mode -
but, I personally like to work with XML over csv if you go in that
direction
I would use in Ed's place direct an SQL Server Express database like the
advice of Scott especially now that this is freeware.
I direct this to you, but it is more for the OP that I write it like this.
I agree that overall, the database is the best solution. But, that
really depends on his hosting provider as to what is available - and
what the OP is willing to learn, do etc. But, given the choice
between working with CSV and XML - I would take the XML.