D
DKode
I will be making a windows app that will run on user's local machines.
It will not be in a networked environment or anything like that which
rules out SQL Server for the database. I am trying to come up with the
best method to store data on the local user machine.
I was thinking of using XML files, but I am concerned about how
quickly the xml files will grow and should I have a seperate XML file
for each table?
Here's a run down of what this program will do :
Users will put a CD in their cd-rom drive, the app will read all the
folder/filenames off the cd and allow them to attach additional
keywords to each folder/filename, then they will give each CD a unique
name and label the CD with this name. Then when they want to search
for a program they will run the app and search for keywords and the
app will tell them which cd to look on.
Hope this is descriptive enough. I was thinking of using MSDE, but
this would require it be running on the user's machine at all times
which I don't like the idea of. That's why I came up with the solution
of XML files but the XML filesize can quickly grow... 100 files per cd
times about 200 cd's average, that's 20,000 records right there, not
too mention the extra keywords for each record that might be added.
Maybe a flatfile would work better?
Any advice/pointers would be appreciated.
Thank you!
It will not be in a networked environment or anything like that which
rules out SQL Server for the database. I am trying to come up with the
best method to store data on the local user machine.
I was thinking of using XML files, but I am concerned about how
quickly the xml files will grow and should I have a seperate XML file
for each table?
Here's a run down of what this program will do :
Users will put a CD in their cd-rom drive, the app will read all the
folder/filenames off the cd and allow them to attach additional
keywords to each folder/filename, then they will give each CD a unique
name and label the CD with this name. Then when they want to search
for a program they will run the app and search for keywords and the
app will tell them which cd to look on.
Hope this is descriptive enough. I was thinking of using MSDE, but
this would require it be running on the user's machine at all times
which I don't like the idea of. That's why I came up with the solution
of XML files but the XML filesize can quickly grow... 100 files per cd
times about 200 cd's average, that's 20,000 records right there, not
too mention the extra keywords for each record that might be added.
Maybe a flatfile would work better?
Any advice/pointers would be appreciated.
Thank you!