31–40 of 63 posts
Earlier quoted context omitted.
It's a free beta. We'll be charging for it down the line, but you can use this however you like for now. (It's not open source, though.)
Why would I use this when I can already connect to Excel using COM for free?
I still have a soft spot for VBA, especially in Excel. I wrote a supply-chain management application in Excel+VBA that's still in production today. As comfortable as I am with VBA, I wouldn't mind in the least ditching it for Python, which makes writing routine methods trivial. Great work!
Glad you like it! We're also backwards compatible - you can keep running old VBA code, and write new scripts in Python.
niiiice! :) python is definitely better than vba, didn't think of this use for it!
I still have a soft spot for VBA, especially in Excel. I wrote a supply-chain management application in Excel+VBA that's still in production today. As comfortable as I am with VBA, I wouldn't mind in the least ditching it for Python, which makes writing routine methods trivial. Great work!
Glad you like it! We're also backwards compatible - you can keep running old VBA code, and write new scripts in Python.
Earlier quoted context omitted.
It's a free beta. We'll be charging for it down the line, but you can use this however you like for now. (It's not open source, though.)
Why would I use this when I can already connect to Excel using COM for free?
http://stackoverflow.com/a/445961
Though I admit scripting Excel from Python should be easier to setup than it is.
The big question I have is why would I use this instead of a real database. If i am not mistaken excel can hook up to ODBC sources and then I can just script things as I normally would using the database drivers.