Posted by Gary Hasler on 10/17/18 11:55
> But why not create a seperate csv (if you really want it seperate) if you're
> already using it's capabilities?
> ...It seems more logical/maintainable to me. It seems even more logical to me
> to keep the price in the original CSV, and to maintain it there. It's not
> that hard to write a framework than can manipulate a csv as easily as a flat
> table.
I agree totally. I store a list of about 40 unit rate prices for our online
quote system as a very small .csv file, and our cost estimating staff can easily
load it in Microsoft Excel and play with it all they want without having to get
into databases at all. When they're finished, I upload it to the server easy as
pie.
Navigation:
[Reply to this message]
|