to database or not to database
-
sorry for the cheesy topic name.... Anyway, i have project with a fairly low data-volume. I am running it off of an access database at the moment. I believe this makes it less portable as the user must have access to use it that way (right???). would i be better off just using a flat file? we're talking about three small tables with a an average of about 6-7 complete records. thanks serenity now, insanity later - lloyd braun
-
sorry for the cheesy topic name.... Anyway, i have project with a fairly low data-volume. I am running it off of an access database at the moment. I believe this makes it less portable as the user must have access to use it that way (right???). would i be better off just using a flat file? we're talking about three small tables with a an average of about 6-7 complete records. thanks serenity now, insanity later - lloyd braun
Hi there. Access .mdb files are actually very good for low volume, desktop (i.e. non-shared) databases. Your code just needs the Jet provider installed on the client machine - which is a standard part of MDAC (as opposed to a full copy of Access). So you're probably just fine using it. Of course, with only six or seven complete records you may do just fine to use an XML file to store your data. If you're using .Net, you could read the file into an XmlDataDocument and treat it as either an XML document or a DataSet.
-
sorry for the cheesy topic name.... Anyway, i have project with a fairly low data-volume. I am running it off of an access database at the moment. I believe this makes it less portable as the user must have access to use it that way (right???). would i be better off just using a flat file? we're talking about three small tables with a an average of about 6-7 complete records. thanks serenity now, insanity later - lloyd braun
Another place to look is the "Quality of Service" layer in Windows. If "to err is human", programmers must be superhuman...
-
Another place to look is the "Quality of Service" layer in Windows. If "to err is human", programmers must be superhuman...
OOPS... Wrong thread! (See thread above) If "to err is human", programmers must be superhuman...