2009/11/11 Adam <[email protected]> > > I need to use a flat file database for a program i am writing (users > needs offline portability). > > What the program does is takes input data calculates a return value > based on certain criteria (ie if value 1 from import is within 0 and 3 > take value 2 and multiply it by the criteria's column value) > > Requirements: > * The INPUT data: imported easily from excel (the input xls can be > forced to be massaged/formatted by implementing SOPs) > * The INPUT data needs to be easily edited after the fact, incase key > values need to me tweaked or a flat increase needs to be applied to > the input values > * The CRITERIA data: imported easily from excel (same SOP can apply > that applied for input) > * The OUTPUT results need to be exportable to excel. > > > Now i am in an argument with the Project Lead as to what FlatFile to > use. He says we should rely heavily on MS ACCESS for importing the > INPUT data, manipulating the INPUT and CRITERIA. > I am railing against the use of MS ACCESS, period. I have a great > disdain for MS ACCESS and i am afraid it is blinding me to the > possibility that MS ACCESS is better to use than writing all the > editing and import functions into the C# program. > > Why are you manipulating the data with Access if you intend to "write a program"?
> What i am asking is, Is Access a good solution for importing/ > manipulating the IMPORT and CRITERIA data?, or should i write the > controls into my program and use something like SQLite for the flat > file? > > SIDE NOTE: i want to keep the business logic layer of the app in C# so > that i can easily redeploy the application installation without needed > to worry about rogue users having outdated business logic code. -- Charles A. Lopez [email protected] Registered Microsoft Partner New York City, NY I'm running on Windows 7 Build 7100 Quality Software Works
