"Excel is not a database." We know the mantra and are living the reality. We have developed great and complex functions in Excel, often times with the help of the generous experts on this board. We use Excel craftily and lovingly. Our data are simple in structure: fixed number of columns, and a growing number of rows. Now we need evolve and stop forcing Excel to be a database, but still avail ourselves of the critical functions we rely on.
We're not sure how to architect this evolution, however. We need to shift to storing our data in mySQL (mandate). None of us has familiarity with db management, nor are we programmers. We will need to learn and/or outsource. But to help me wireframe the process, are the steps: translate our Excel functions into Language X --> apply them to data in the database --> export the results to Excel (for further analysis)? Or other? (No such thing as an Excel function --> mySQL query converter I wager.) It seems the import/export piece is not the mysterious piece in this puzzle, but how we apply our Excel functions to the data in mySQL is. Any helpful guidance would be truly appreciated!
We're not sure how to architect this evolution, however. We need to shift to storing our data in mySQL (mandate). None of us has familiarity with db management, nor are we programmers. We will need to learn and/or outsource. But to help me wireframe the process, are the steps: translate our Excel functions into Language X --> apply them to data in the database --> export the results to Excel (for further analysis)? Or other? (No such thing as an Excel function --> mySQL query converter I wager.) It seems the import/export piece is not the mysterious piece in this puzzle, but how we apply our Excel functions to the data in mySQL is. Any helpful guidance would be truly appreciated!