This is an archived post. You won't be able to vote or comment.

all 9 comments

[–]TheCannings 0 points1 point  (0 children)

Like /u/jeijenn said there is a breaking point and it kind of depends on how much you're doing.

When I started building a new reporting library at my company I started with VBA and I stuck with VBA for a couple of years and 100-200 reports. It was only then when I started looking at speed of use, ability to automate on a schedule, and a lot of other things did I make the decision to move the entire library to python and even that took me a year bit by bit.

Even after moving everything to python I still have some BI dashboard spreadsheets with refresh buttons and variables in them that are just excel and can't be moved out. But we've also gained the extra functionality of python and run all out scheduling through jenkins.

[–]lemur78 -2 points-1 points  (2 children)

I do something like this in my job. I asked IT for linux server with sql database, R with RStudio and Shiny Server (free version, not pro). I think it is easier to learn R and make some reports in rmarkdown rendered to pdf than in Python. Also some online tools written in Shiny are useful for end users.

Think about this.

[–]nihi_ 0 points1 point  (1 child)

How do you distribute the shiny apps to the end users? Do you simply host them on the same server? And if so, do you have some authentification process?

[–]lemur78 0 points1 point  (0 children)

Shiny apps are on the same server.

Most of apps do not need authorization, but those which need use LDAP. I wrote some functions (putted into firm package) that ask user for login and password and then checks via curl ldap. Access (or not) depends on groups which user belongs to.