in reply to A good way to input data into a script w/o an SQL database

Your intuition that the code and data should be separated is correct. Data usually falls into one of two categories which should also be kept separate. In the first, any change makes all previous version obsolete. In the other, you have several versions of the data in production at the same time. (e.g. one version for each customer, user, location, etc.) Changes to each version can be made independently, but are probably rare. The choice of technology to store each type of data is not very important. Ideally, it should be easy for the responsible person(s)? to view and/or change the data, and difficult for anyone else. In making that choice, You also must consider what resources are shared by users of the data. Are they all on one computer, one LAN, or internet? Is it possible to share a data base?

I hope I have been a help in specifying the kind of information we need in order to help you.