jwcolby
jwcolby at colbyconsulting.com
Tue Nov 8 16:55:49 CST 2011
Oh yea, performance on any modern computer would be instantaneous with that little data. It wouldn't scale well though. John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 11/8/2011 2:31 PM, newsgrps wrote: > Thanks John, > > Would 50 fields (mixture of text and numbers) and 200 records be considered small? > > Not having dealt with XML before, would the idea be to load the table at the beginning of a session > and then save it at the end (or at regular intervals)? > > David > > At 9/11/2011, jwcolby wrote: >> For small tables using XML to the local directory would be just fine. >> >> John W. Colby >> Colby Consulting >> >> Reality is what refuses to go away >> when you do not believe in it >> >> On 11/8/2011 2:04 PM, newsgrps wrote: >>> This is sort of off topic but I will give it a shot. >>> >>> I am considering learning dot net and thought I would do a simple windows application project that >>> can be distributed that has a single table of address information (perhaps being expanded to up to 5 >>> tables). >>> >>> My reading indicates that I can create an installable package ok but I am unsure about the database >>> part. I have seen examples which use SQL Server or Access but both of these seem overkill in this >>> situation - likely users will not have either of these installed and it seems crazy to include >>> runtime installations just for one table (or even if there were up to 5 tables). >>> >>> Assuming that a similar application was created for actual distribution what would be a suitable >>> solution for storing the data in these circumstances (or is a dot net application not the right tool >>> for this job?) >>> >>> >>> Regards >>> >>> David Emerson >>> Dalyn Software Ltd >>> Wellington, New Zealand >